Wireshark-bugs: [Wireshark-bugs] [Bug 6732] New: megaco.context==x appears to interpret x's type
Date: Thu, 12 Jan 2012 15:11:40 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6732

           Summary: megaco.context==x appears to interpret x's type
                    differently below a certain value
           Product: Wireshark
           Version: 1.6.2
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: ericus@xxxxxxxxx


Created attachment 7679
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=7679
Sample packet capture described in the bug

Build Information:
Version 1.6.2 (SVN Rev 38931 from /trunk-1.6)

Copyright 1998-2011 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (32-bit) with GTK+ 2.22.1, with GLib 2.26.1, with WinPcap (version
unknown), with libz 1.2.5, without POSIX capabilities, without libpcre, with
SMI
0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.10.3,
with
Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
Sep
 7 2011), with AirPcap.

Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.2
(packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.10.3, Gcrypt 1.4.6, without AirPcap.

--
See attached sample capture with sample packets from two different H.248
contexts (383 and 54). When using the display filter megaco.context==383 in
this capture file, the three packets corresponding to context 383 are
displayed. When using display filter megaco.context==54 in the file, no packets
are displayed, even though there are three packets in the file from context 54.

However, putting 54 in double quotes " " causes the filter to work. These
double quotes are *not* required for the filter to work with context 383,
leading me to believe that below a certain threshold (maybe less than three
digits?) wireshark is possibly interpreting the value as a number instead of a
string, so it doesn't work. 

This should at least be consistent one way or another, and preferably should
work without quotes entirely, for this display filter.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.