Re: use of radiotap bit 14?

Johannes Berg <[email protected]>
Newsgroups org.netbsd.radiotap
Message-ID <[email protected]>
On Thu, 2008-06-19 at 12:33 -0700, Guy Harris wrote:
> 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.

Ok, cool. Yes, we use the RX flags meaning for bit 14. I guess we
shouldn't have started doing that but that stuff was there before I
understood the issue.

johannes
signature.asc (application/pgp-signature, 836 B)
-----BEGIN PGP SIGNATURE-----
Comment: Johannes Berg (powerbook)

iQIcBAABAgAGBQJIWrq6AAoJEKVg1VMiehFYXzIQAMFukfqdp/4VsMpATGdAO15K
TT3+7cRxzWQZ7mZUInTmNZrbQDFGtI2iEltVaGrAXIauh3v6D/y8z9W3ntjaCm76
ymtzbC7uvBZEeBl4u+SVxR2fRoTSDxbIq/0T2hhB4IMQGPyNEsQo7wcFjPMSKCDe
sgJ1srIMy9aqJiXsfBfC0Wu3HfqJ6p6BHYk3GpF6inZB+0R7usmQCCGNOxq7jfzC
1QxAusdsRajVy7nzscUGeZidb5hl1ZtU7UnJrctkC/ppWFnot5Epg2eGrJ2MjXPg
hBvugZ0IRRt7z5rFvCJFK7qgsqwbhrp40aIKS07b6Q/sPWryCtP1YK9JlaTGbjSh
Q76zgMKTkjA/gtBk/B7Bl7NDvPpH8m0F6K8zm78hFzDQSx9cr4H+UrVEPRcGHggI
Jif01iosk7n7TIIUbFY5/qRDQzmMF4kqentSkDrSHQrS5/vtCGHJylg1pX89usu3
wXDuP5VmLiHxtV29jCytmXxFcdwEMZK/BRrhkKXf8qrkUV7ZLroGl5WhnbnXuZCS
VpQMbDS7GBiRZLjC1BJLGFO/WRSn1z/pJktTS3JE31iR52Rf1SonipLvk7cuk9JS
HYat5FUCz70B8mEuRUqHnYBxH9ptSi2ko3Nxw286Lv4swYbJ5VW3gzJPxjtGzDzs
dr384wT7hwFNMN1txz+z
=4MqG
-----END PGP SIGNATURE-----
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.