Re: [Wireshark-dev] Should I create virtual fields for use in display filters

2006-12-02 Thread Hal Lander
wireshark-dev@wireshark.org Subject: Re: [Wireshark-dev] Should I create virtual fields for use in display filters Date: Sun, 26 Nov 2006 11:14:48 -0800 Hal Lander wrote: I would like to give users of my dissector a quick and easy way to find any packets that have been sent which

Re: [Wireshark-dev] Should I create virtual fields for use in display filters

2006-12-02 Thread Guy Harris
Hal Lander wrote: How does tvb_reported_length() know the actual length of the packet if the full packet was not captured? Because the full packet was received; it was just cut short in the process of supplying it to the capture mechanism (i.e., all the packet data was available, but only

Re: [Wireshark-dev] Should I create virtual fields for use in display filters

2006-11-27 Thread Jeff Morriss
Guy Harris wrote: Hal Lander wrote: I would like to give users of my dissector a quick and easy way to find any packets that have been sent which are not of the expected size. To me, as a newbie, the obvious way to do this would be to allow them to filter packets based on expected and

[Wireshark-dev] Should I create virtual fields for use in display filters

2006-11-26 Thread Hal Lander
I would like to give users of my dissector a quick and easy way to find any packets that have been sent which are not of the expected size. To me, as a newbie, the obvious way to do this would be to allow them to filter packets based on expected and actual packet sizes. To do that I think I