Wireshark-bugs: [Wireshark-bugs] [Bug 13244] New: Errors in 802.11ad dissector

Date: Tue, 13 Dec 2016 15:56:38 +0000
Bug ID 13244
Summary Errors in 802.11ad dissector
Product Wireshark
Version 2.2.2
Hardware x86-64
OS Ubuntu
Status UNCONFIRMED
Severity Normal
Priority Low
Component Dissection engine (libwireshark)
Assignee [email protected]
Reporter [email protected]

Created attachment 15127 [details]
Capture File

Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
Hi,

I have the attached file which contains a capture for an ongoing wireless
communication between two 802.11ad enabled devices using Wilocity Chipset. In
the trace, we can the following fields are not decoded correctly:

1. Grant Frame (Figure 8-29c in the standard):
The frame contains Dynamic Allocation Info Field which is 5 bytes in length,
however the 802.11ad dissector interprets it as Response Offset field which is
2 bytes in length.

2. BRP Frame (Table 8-281ag):
This frame is an Action No Ack Frame. It compromises the following information
fields:
A. BRP Request Field.
B. DMG Beam Refinement Element.
C. OptionalChannel Measurement Feedback element.

In the trace, you can see that the DMG Beam Refinement Element is not decoded
correctly.

2. The SSW-Feedback field (8.4a.3):
This field is utilized in different frames and depending on where it is used it
has different format whether it is transmitted as part of an ISS or not.
However, in the trace file you can see that the field in always decoded using
the same format (The one of when it is transmitted as part of ISS) in SSW,
SSW-Feedback, and SSW-ACK Frames. The correct thing to do is the following:

A. In the SSW Frames, if the Direction in the Sector Sweep Field is set to
beamforming initiator then we use the Format of when transmitted as part of
ISS. Whereas, if the Direction is beamforming responder we use the other
format.

B. For the SSW-Feedback and SSW-ACK, we use the format of when not transmitted
as part of an ISS.


You are receiving this mail because:
  • You are watching all bug changes.