http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1371
Summary: BSSGP dissector: incorrect TLLI field name handling
Product: Wireshark
Version: SVN
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Major
Priority: Medium
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: pilyuk@xxxxxxxxx
Build Information:
Version 0.99.6-SVN-20777 (SVN Rev 20777)
Copyright 1998-2007 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 with GTK+ 2.10.7, with GLib 2.12.7, with WinPcap (version unknown),
with libz 1.2.3, with libpcre 6.4, with Net-SNMP 5.4, with ADNS, with Lua 5.1,
with GnuTLS 1.6.1, with Gcrypt 1.2.3, with MIT Kerberos, with PortAudio
PortAudio V19-devel, with AirPcap.
Running on Windows XP Service Pack 2, build 2600, with WinPcap version 4.0
(packet.dll version 4.0.0.755), based on libpcap version 0.9.5, without
AirPcap.
Built using Microsoft Visual C++ 6.0 build 8804
--
When clicking on the TLLI in packet details window and trying to apply it as a
filter, Wireshark uses incorrect field name (bssgp.iei.nacc_cause instead of
bssgp.tlli) and instead of the actual TLLI value, 0x1f is put into the filter
string. Trying to enter the value by hand makes no result (empty packet list
after the apply). Using the "bssgp.tlli" field identifier in filter string is
not functional either.
Protocol hierarchy: Frame-Ethernet-802.1Q-IP-UDP-NSIP-BSSGP-...
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.