Wireshark-bugs: [Wireshark-bugs] [Bug 4160] New: Minor bug fixes for packet-eigrp.c
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4160
Summary: Minor bug fixes for packet-eigrp.c
Product: Wireshark
Version: SVN
Platform: Other
OS/Version: All
Status: NEW
Severity: Major
Priority: Medium
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: jochen.bartl@xxxxxxxxx
Build Information:
wireshark 1.3.1 (SVN Rev 30683 from /trunk)
Copyright 1998-2009 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.1, with GLib 2.20.1, with libpcap 1.0.0, with libz
1.2.3.3, with POSIX capabilities (Linux), with libpcre 7.8, with SMI 0.4.7,
without c-ares, with ADNS, with Lua 5.1, without Python, with GnuTLS 2.4.2,
with
Gcrypt 1.4.1, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
Mar
4 2009), without AirPcap, with new_packet_list.
Running on Linux 2.6.28-15-generic, with libpcap version 1.0.0, GnuTLS 2.4.2,
Gcrypt 1.4.1.
Built using gcc 4.3.3.
--
This patch fixes the display filter for the prefix length of IPv6 external
route updates and the length calculation of the destination address in IPv6
route updates. It is related to the patch introduced in svn revision 29473 [1].
After having a look at some pcap files I realized that the dissector
highlightes sometimes to less bytes in the hex view, when the destination field
in IPv6 route updates is selected. I found out that the destination field
length (addr_len) must be incremented by 1 byte if the prefix length is 0, 8,
16, 24, 32, 40, 48, 56, 64, 72, 80, 88, 96, 104, 112, or 120.
You can verify this behaviour by having a look at
http://verbosemo.de/~lobo/files/eigrp-ipv6-introute-dst.pcap
Best Regards,
Jochen
1) http://anonsvn.wireshark.org/viewvc?view=rev&revision=29473
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.