Re: Bad FCS flag

Johannes Berg <[email protected]> Fri, 05 Sep 2008 22:44:08 +0200

Newsgroups	org.netbsd.radiotap
Message-ID	<[email protected]>

> TCPDump uses this bit, too.  I think that we are stuck with it.

Alright. I'll amend my old proposal to drop the shortGI bit for now (not
interested in 11n, let somebody else define those things) and make this
the "bad FCS" bit rather than the first bit in "RX flags".

> >  * the unofficial RX-flags stuff defines that bit 0 in "RX flags" means
> >    "bad FCS"
> 
> Any users of this bit?

Not sure, I think we might create it in Linux, but it's easy to change.

> I think that TCPDump & Wireshark probably out-number the radiotap
> interpreters who use the rx-flags bit :-), but I don't know how many
> drivers there are who write headers with "bad FCS" in the rx flags bit.

Yeah. I'll mark the RX flags bit as reserved though so we don't run into
odd things there.

johannes

signature.asc (application/pgp-signature, 836 B)