Re: [RFA] HT extensions

Johannes Berg <[email protected]>
Newsgroups org.netbsd.radiotap
Message-ID <[email protected]>
On Tue, 2010-10-05 at 13:21 -0500, David Young wrote:

> > The "known" field indicates which flags are known:
> > 
> > 0x01: bandwidth
> > 0x02: MCS index known (in `mcs` part of the field)
> > 0x04: guard interval
> > 0x08: HT format
> > 0x10: FEC type
> > 0x20: a-MPDU status
> > 0x40: a-MPDU beginning/end
> > 0x80: reserved
> > 
> > The `flags` is any combination of the following:
> > 0x03: bandwidth - 0: 20, 1: 40, 2: 20L, 3: 20U
> > 0x04: short GI
> > 0x08: 0: mixed, 1: greenfield
> > 0x10: 0: BCC, 1: LDPC
> > 0x20: a-MPDU status - 0: not part of an a-MPDU, 1: part of a-MPDU
> > 0x40: 0: first frame, 1: last frame
> > 0x80: reserved
> 
> Suggestion for clarity: name each of the flags in the "flags" field, and
> in the definition of the "known" field, indicate corresponding flags by
> name.

Yes, that'd help, good plan, I'll make some wiki edits and resend.

> How can an application use the first/last-frame information?

Well, right now my wireshark patch is simply displaying it, but it could
also link up frames of an a-MPDU so you can jump between them, and with
this it can know what the framing was. If you just know a frame was part
of an aMPDU you won't know which one, this should help.

johannes
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.