https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5261
Summary: EIGRP dissection error in Flags field in external
route TLVs
Product: Wireshark
Version: 1.4.0
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: sean.van.gorder@xxxxxxxxx
Created an attachment (id=5223)
--> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=5223)
Example packets
Build Information:
Version 1.4.0 (SVN Rev 34005 from /trunk-1.4)
Copyright 1998-2010 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.16.6, (32-bit) with GLib 2.22.4, with WinPcap (version
unknown), with libz 1.2.3, 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.8.5, with
Gcrypt 1.4.5, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
Aug
29 2010), 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.8.5, Gcrypt 1.4.5, without AirPcap.
Built using Microsoft Visual C++ 9.0 build 30729
--
The individual flags in eigrp.ip_ext.flags, eigrp.at_ext.flags, and
eigrp.ip6_ext.flags are reading their values from the wrong byte. This is
easily demonstrated in Wireshark, as selecting the "Flags" line highlights the
correct byte in the hex view, but individual flag lines highlight a different
byte, and display values based on that byte instead.
Can't confirm yet, but it seems the fix would be to use the offset variable
instead of 0 when calling proto_tree_add_item on the individual flags.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
