Wireshark mailing list archives

Re: tcap.tid display filter not applied as byte string

From: Jeff Morriss <jeff.morriss.ws () gmail com>
Date: Wed, 25 Jul 2012 11:40:39 -0400

Christopher Maynard wrote:

Arjan Van Der Oest <Arjan@...> writes:

When using the TCAP dissector and clicking right on a TID value (i.e.:

0c0013c0) , selecting "Apply as Filter > Selected" the display filter will be
composed as "tcap.tid == 0c0013c0" and WS will error on me with "tcap.tid ==
0c0013c0" isn't a valid display filter: &quot;0c0013c0&quot; is not a valid byte
string.

When manually changing the display filter to  "tcap.tid == 0c:00:13:c0 the

problem is solved. It seems to me the 'Apply as filter...' command from the
context menu is not behaving correctly.

Please file a bug report and include a small capture file for testing.

Of particular interest would be the Wireshark version; 1.8.0 and trunk(1.9.0) don't show this problem. Upgrading might be a simpler solution :-).

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request () wireshark org?subject=unsubscribe

Current thread:

tcap.tid display filter not applied as byte string Arjan Van Der Oest (Jul 18)
- Re: tcap.tid display filter not applied as byte string Christopher Maynard (Jul 18)
  - Re: tcap.tid display filter not applied as byte string Jeff Morriss (Jul 25)