From: Guy Harris <guy-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
To: radiotap <radiotap-rN9S6JXhQ+WXmMXjJBpWqg@public.gmane.org>
Subject: Re: use of radiotap bit 14?
Date: Thu, 19 Jun 2008 12:33:47 -0700 [thread overview]
Message-ID: <485AB49B.4080403@alum.mit.edu> (raw)
In-Reply-To: <1213902633.8967.84.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
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.)
next prev parent reply other threads:[~2008-06-19 19:33 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 22:16 use of radiotap bit 14? Johannes Berg
[not found] ` <1188512214.7585.3.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2007-08-31 14:47 ` Pavel Roskin
2007-08-31 16:23 ` Sam Leffler
[not found] ` <46D84073.3090709-zZXckVAlHaQAvxtiuMwx3w@public.gmane.org>
2007-08-31 16:33 ` Sam Leffler
2007-08-31 16:50 ` Gerald Combs
[not found] ` <46D846E4.20103-IZ8446WsY0/dtAWm4Da02A@public.gmane.org>
2007-08-31 21:57 ` Johannes Berg
[not found] ` <1188597475.7585.46.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2007-08-31 22:17 ` Pavel Roskin
2007-09-12 17:17 ` David Young
[not found] ` <20070912171755.GA17887-eZ+MEZF6i8Dc+919tysfdA@public.gmane.org>
2007-09-12 19:21 ` Gerald Combs
2007-09-13 7:18 ` Johannes Berg
[not found] ` <1189667921.6161.86.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2007-11-26 16:58 ` Johannes Berg
[not found] ` <1196096301.4149.309.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2007-11-26 18:13 ` David Young
[not found] ` <20071126181329.GA3568-eZ+MEZF6i8Dc+919tysfdA@public.gmane.org>
2007-11-27 13:21 ` Johannes Berg
2007-09-12 18:06 ` David Young
[not found] ` <20070912180619.GB17887-eZ+MEZF6i8Dc+919tysfdA@public.gmane.org>
2007-09-12 19:03 ` Pavel Roskin
2007-09-13 18:06 ` David Young
[not found] ` <20070913180618.GK17887-eZ+MEZF6i8Dc+919tysfdA@public.gmane.org>
2007-09-13 18:15 ` Guy Harris
2007-09-13 7:29 ` Johannes Berg
[not found] ` <1189668582.6161.91.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2007-10-07 23:55 ` David Young
[not found] ` <20071007235551.GN6429-eZ+MEZF6i8Dc+919tysfdA@public.gmane.org>
2007-10-08 9:45 ` Johannes Berg
[not found] ` <1191836708.4063.17.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-06-19 16:13 ` Johannes Berg
2007-12-11 23:09 ` Johannes Berg
2007-12-12 17:27 ` Johannes Berg
2008-06-19 18:10 ` Johannes Berg
[not found] ` <1213899026.8967.56.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-06-19 18:41 ` Johannes Berg
2008-06-19 17:44 ` Johannes Berg
[not found] ` <1213897499.8967.46.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-06-19 17:59 ` Johannes Berg
[not found] ` <1213898387.8967.54.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-06-19 18:28 ` Gerald Combs
[not found] ` <485AA531.4010408-IZ8446WsY0/dtAWm4Da02A@public.gmane.org>
2008-06-19 18:34 ` Guy Harris
[not found] ` <485AA6C3.8090303-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
2008-06-19 18:37 ` Johannes Berg
2008-06-19 20:05 ` Johannes Berg
2008-06-19 18:13 ` Pavel Roskin
2008-06-19 18:18 ` Johannes Berg
[not found] ` <1213899529.8967.62.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-06-19 18:39 ` Pavel Roskin
2008-06-19 18:43 ` Johannes Berg
2008-06-19 18:56 ` David Young
[not found] ` <20080619185646.GA17738-eZ+MEZF6i8Dc+919tysfdA@public.gmane.org>
2008-06-19 19:10 ` Johannes Berg
[not found] ` <1213902633.8967.84.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-06-19 19:33 ` Guy Harris [this message]
[not found] ` <485AB49B.4080403-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
2008-06-19 19:59 ` Johannes Berg
2008-06-19 19:39 ` David Young
[not found] ` <20080619193958.GB17738-eZ+MEZF6i8Dc+919tysfdA@public.gmane.org>
2008-06-19 19:51 ` Guy Harris
[not found] ` <485AB8B0.7060606-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
2008-06-19 20:06 ` Loris Degioanni
[not found] ` <485ABC4A.4060801-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-06-19 20:17 ` Guy Harris
2008-06-19 20:25 ` Johannes Berg
2008-07-01 16:35 ` use of radiotap bit 14? [mostly 11n] Sam Leffler
2008-06-19 20:06 ` use of radiotap bit 14? Johannes Berg
2008-06-19 22:33 ` Scott Raynel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=485AB49B.4080403@alum.mit.edu \
--to=guy-frubxkncsvf2fbvcvol8/a@public.gmane.org \
--cc=radiotap-rN9S6JXhQ+WXmMXjJBpWqg@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox