| Bug ID |
11053
|
| Summary |
Interface Identifier incorrectly represented by Wireshark
|
| Product |
Wireshark
|
| Version |
1.12.4
|
| Hardware |
x86
|
| OS |
Windows XP
|
| Status |
UNCONFIRMED
|
| Severity |
Minor
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 13505 [details]
IPv6CP packets with a wrong Interface Identifier presentation in Wireshark
Build Information:
Version 1.12.4 (v1.12.4-0-gb4861da from master-1.12)
Copyright 1998-2015 Gerald Combs <[email protected]> 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.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.2.15, with Gcrypt 1.6.2,
with
MIT Kerberos, with GeoIP, with PortAudio V19-devel (built Mar 4 2015), with
AirPcap.
Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.3
(packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 3.2.15, Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz, with 2046MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
Some IPv6CP Interface Identifier values (RFC 5072) from .pcap traces are not
correctly represented by Wireshark. The data (hex) field in the bottom of the
Wireshark window is however correct. For example:
1)
Interface Identifier: 0230:88ff:fe4:00b3 <<<< IS: Identifier representation
in Wireshark (presentation failure!)
Interface Identifier: 0230:88ff:fe04:00b3 <<<< SHOULD: correct Hex code in the
data / trace
2)
Interface Identifier: 55aa:0102:031:0000 <<<< IS: Identifier representation
in Wireshark (presentation failure!)
Interface Identifier: 55aa:0102:0301:0000 <<<< SHOULD: correct Hex sequence
in the data / trace
PPP-over-Ethernet Session
0001 .... = Version: 1
.... 0001 = Type: 1
Code: Session Data (0x00)
Session ID: 0x0001
Payload Length: 16
Point-to-Point Protocol
Protocol: IPv6 Control Protocol (0x8057)
PPP IPv6 Control Protocol
Code: Configuration Ack (2)
Identifier: 1 (0x01)
Length: 14
Options: (10 bytes), Interface Identifier
Interface Identifier: 55aa:0102:031:0000 <<<< presentation failure!
0000 00 0a 5e 01 00 00 00 19 e2 ba 30 2d 81 00 c2 d0 ..^.......0-....
0010 81 00 c0 80 88 64 11 00 00 01 00 10 80 57 02 01 .....d.......W..
0020 00 0e 01 0a 55 aa 01 02 03 01 00 00 00 00 00 00 ....U...........
0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
55 aa 01 02 03 01 00 00 <<< correct Hex sequence in the data / trace
You are receiving this mail because:
- You are watching all bug changes.