I have the following snapshot for a capture for 802.11ad DMG Access Point generated by ns3 simulator: While going through the fields of the DMG Beacon, the wire-shark interprets part of the information in a wrong way. For example in the fixed parameter Sector Sweep field (3 Bytes), I pass the following information in the DMG Beacon during my simulation:
As a result, the encoding of this information according to the standard as illustrated in the following figure should be as following: Byte (0) Byte (1) Byte (2) 00010000 00000100 00000001 In more details:
Note: The left most bit is the most significant bit. So as you can see the wireshark dissector interprets them i the opposite way. asked 04 Aug '15, 09:35 Hany Assasa |
2 Answers:
Bug 11419 was filed, and it is now fixed. answered 05 Aug '15, 19:16 Guy Harris ♦♦ |
Bugs should be reported via the Wireshark Bug Database. Include as much info as possible (like here), and at least a capture file of the relevant traffic. answered 05 Aug '15, 00:14 Jaap ♦ |
Wireshark version?
I am running Wireshark (1.12.6) on Linux @grahamb