Re: [Wireshark-dev] Global conversation

2011-10-08 Thread Guy Harris
On Oct 7, 2011, at 5:51 AM, Anders Broman wrote: > I've been contemplating the idea of making it possible to filter a "call" in > the Telco world that could involve > A multitude of protocols for example SIP, DIAMETER, H248, ISUP, BICC and a > number of Mobile protocols. I suppose this is > Wha

Re: [Wireshark-dev] Send info to plugin

2011-10-08 Thread Guy Harris
On Oct 7, 2011, at 4:40 AM, Martin Kaiser wrote: > Thus wrote Guy Harris (g...@alum.mit.edu): (At this point, I really wish my name were Zarathustra. :-)) > I've been > playing with a new port_type PT_DVBCI_SESSION_NUMBER and set both source > and destination port to the session number. Does th

Re: [Wireshark-dev] Send info to plugin

2011-10-08 Thread Guy Harris
On Oct 7, 2011, at 2:27 AM, fa...@freesurf.fr wrote: > Typically a filename + Directory where the the plugin dissector would > write some statistic information. If those are statistics about the protocol, that sort of work is best done in a tap, rather than a dissector; dissectors should just d

Re: [Wireshark-dev] Correct and efficient way of displaying bit fields?

2011-10-08 Thread Guy Harris
On Oct 7, 2011, at 2:22 PM, Kaul wrote: > I'm struggling for some time now with displaying bitfields, I'm sure there > must be something I'm overlooking, or it's just a bit difficult to do in > Wireshark. > > I have a 32bit, little endian field, which I'd like to parse the bits (as > set/not

Re: [Wireshark-dev] syntax errors are eating my time and brain though my code is almost correct

2011-10-08 Thread Jakub Zawadzki
Hi, On Sat, Oct 08, 2011 at 01:25:35PM +0530, prashanth sappidi wrote: > [...] specifies undefined struct/union 'trigger_structure' > ... > /* MY_CODE BEGIN */ > typedef struct _trigger_structure { > intrestart_trigger; > gint64 trigger_temp; > inttrigger_temp2; >

Re: [Wireshark-dev] Correct and efficient way of displaying bit fields?

2011-10-08 Thread Helge Kruse
Am 07.10.2011 23:22, schrieb Kaul: I'm struggling for some time now with displaying bitfields, I'm sure there must be something I'm overlooking, or it's just a bit difficult to do in Wireshark. I have a 32bit, little endian field, which I'd like to parse the bits (as set/not set): Example: 05 00