Re: use of radiotap bit 14?

Guy Harris <guy-FrUbXkNCsVf2fBVCVOL8/[email protected]>
Newsgroups org.netbsd.radiotap
Message-ID <[email protected]>
Johannes Berg wrote:

> Problem is, wireshark actually takes bit 14 to mean "FCS in header".
> Easily changed though if Gerald is willing to take such a patch, I can
> cook up a patch to make it parse the fields above.

OpenBSD defines 14 as IEEE80211_RADIOTAP_FCS.  However, a search through 
the top-of-CVS-tree OpenBSD kernel code shows nothing that *uses* that 
presence bit, and neither top-of-tree FreeBSD nor NetBSD use it (I 
assume from what Sam Leffler said that no FreeBSD release did, and given 
that NetBSD uses it for other purposes I assume no NetBSD release did), 
and I assume, given that you're proposing this, that Linux doesn't use 
it for that purpose.

Given that I've gotten no response from the OpenBSD people from my mail 
and bug report about presence-bit collisions, I'd say Wireshark should 
conform to the standard, and if that breaks analysis of captures from 
OpenBSD systems, too bad.

(If that becomes an issue serious enough to care about, we could either 
get a new DLT_ value for standard radiotap headers, and use that, or rev 
the radiotap header version, but that wouldn't help with existing captures.)
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.