Wireshark-bugs: [Wireshark-bugs] [Bug 10786] VHT NDP announcement frame's STA info field and FCS

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 22 Jan 2015 22:19:09 +0000

Comment # 7 on bug 10786 from 
Hi Alexis,

I am using development wireshark version 1.99.1 (v1.99.1-0-g4c229ca from
master) and observe the below STA info field interpretation in the decode. I
think the 

>From the spec:
B0 .. B11 - AID12
B12 - Feedback Type
B13 .. B15 - Nc Index

For example, currently observed:
STA Info: 0xa4ec
        .... 0100 1110 1100 = AID12: 0x04ec
        ...0 .... .... .... = Feedback Type: SU feedback requested
        101. .... .... .... = Reserved: 0x0005

a4ec here is interpreted as 'a' being most significant byte and 'c' being least
significant byte

Expected:
STA Info: 0xa4ec
        .... 1100 1010 0100 = AID12
        ...0 .... .... .... = Feedback Type
        111. .... .... .... = Reserved

In my test I have a client with assoc ID of 2.

Observed:
STA Info: 0x0200
.... 0010 0000 0000 = AID12: 0x0200
...0 .... .... .... = Feedback Type: SU feedback requested
000. .... .... .... = Reserved: 0x0000

But here expected is the following:
STA Info: 0x0200
.... 0000 0000 0010 = AID12
...0 .... .... .... = Feedback Type: SU feedback requested
000. .... .... .... = Reserved: 0x0000

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