| Bug ID |
12072
|
| Summary |
Wrong interpretation of Instance ID value in OSPFv3 packet
|
| Product |
Wireshark
|
| Version |
2.0.1
|
| Hardware |
x86-64
|
| OS |
Gentoo
|
| Status |
UNCONFIRMED
|
| Severity |
Minor
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 14301 [details]
OSPFv3 packet for IPv4 unicast AF
Build Information:
Version 2.0.1 (SVN Rev Unknown from unknown)
Compiled (64-bit) with GTK+ 3.18.6, with Cairo 1.14.6, with Pango 1.38.1, with
libpcap, with POSIX capabilities (Linux), with libnl 3, with libz 1.2.8, with
GLib 2.46.2, without SMI, without c-ares, without ADNS, without Lua, with
GnuTLS
3.3.20, with Gcrypt 1.6.4, without Kerberos, without GeoIP, without PortAudio,
without AirPcap.
Running on Linux 4.3.3-gentoo, with locale en_US.utf8, with libpcap version
1.7.4, with libz 1.2.8, with GnuTLS 3.3.20, with Gcrypt 1.6.4.
Intel(R) Core(TM) i5 CPU M 460 @ 2.53GHz (with SSE4.2)
Built using gcc 4.9.3.
--
Dear developers, according to rfc5838, Instance ID values should be interpreted
as follows:
Instance ID # 0 - # 31 IPv6 unicast AF
Instance ID # 32 - # 63 IPv6 multicast AF
Instance ID # 64 - # 95 IPv4 unicast AF
Instance ID # 96 - # 127 IPv4 multicast AF
Instance ID # 128 - # 255 Unassigned
But Wireshark reports value of 0x40 (64) as IPv6 multicast AF. Captured file is
attached. Many thanks in advance!
You are receiving this mail because:
- You are watching all bug changes.