On Wed, Jul 24, 2013 at 3:49 AM, Fabiano Ricci wrote:
>
>
> I made a mistake in my last message.
>
> The third argument of the enum is obviously an int value (the same of the
> global_bit_order). You should use a define.
>
> So the enum is:
>
> #define LITTLE 0
> #define BIG 1
>
Just a note that
Fabiano Ricci writes:
> > You can let the user configure the filter by preferences.
A preference is a good idea; however, it does require that the user manually
change it to match the packets, and it doesn't allow for both big-endian and
little-endian packets to be analyzed within the same captu
I made a mistake in my last message.
The third argument of the enum is obviously an int value (the same
of the global_bit_order). You should use a define.
So the enum is:
#define LITTLE 0
#define BIG 1
const en
Hi,
You can let the user configure the filter by preferences.
You can find many infos here: http://wiki.wireshark.org/Preferences and
in the README.dissector file.
EX:
//creates and initialize a global var
static gint global_bit_order = 0;
//creates an enumeration with your options
const enu
Hello all,
I have create a plugin to dissect protocol in TCP payload which is in big
endian format.
But some time due to different architecture of server and client I get data
in little endian format.
I can write code for that as well, but I like that user can provide comment
like if my capture
