From: David Young <dyoung-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
To: radiotap-rN9S6JXhQ+WXmMXjJBpWqg@public.gmane.org
Subject: Re: WiMAX extensions
Date: Wed, 27 Jun 2007 20:10:44 -0500 [thread overview]
Message-ID: <20070628011044.GD23293@che.ojctech.com> (raw)
In-Reply-To: <2A4D4978-D308-40EA-89D5-A2304A5947C7-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
On Wed, Jun 27, 2007 at 04:45:04PM -0700, Guy Harris wrote:
>
> On May 28, 2007, at 10:34 AM, Charles Clancy wrote:
>
> >Suggested new fields:
>
> ...
>
> >- received frequency (in kHz, MHz is not specific enough)
>
> So that'd be an alternative to IEEE80211_RADIOTAP_CHANNEL and
> IEEE80211_RADIOTAP_XCHANNEL, both of which give the frequency in MHz?
>
> (BTW, the current FreeBSD ieee80211_radiotap.h defines
> IEEE80211_RADIOTAP_XCHANNEL as 14 and the current NetBSD
> ieee80211_radiotap.h defines IEEE80211_RADIOTAP_RX_FLAGS as 14.
> Hopefully one or the other of those is *NOT* currently being used, as
> that means that tcpdump, Wireshark, etc. can't handle a property with
> a code of 14 *AND*, at least as I understand the way radiotap works,
> can't handle anything after 14, either, as they don't know how long
> that property is. NetBSD and OpenBSD also collide on the value of 14,
> as well as values after it.)
Guy, your understanding is correct. The divergence is not good for
anyone. The responsible people in OpenBSD and FreeBSD should bring
proposals to the list in order to get presence bits assigned.
Dave
--
David Young OJC Technologies
dyoung-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org Urbana, IL * (217) 278-3933 ext 24
prev parent reply other threads:[~2007-06-28 1:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 6:23 WiMAX extensions Charles Clancy
[not found] ` <50721.65.74.1.247.1178691838.squirrel-2RFepEojUI1Vf4MZnIYnAze48wsgrGvP@public.gmane.org>
2007-05-13 3:32 ` David Young
[not found] ` <20070513033218.GL20770-eZ+MEZF6i8Dc+919tysfdA@public.gmane.org>
2007-05-28 17:34 ` Charles Clancy
[not found] ` <465B128D.9070904-VX+DGZyGJwM3uPMLIKxrzw@public.gmane.org>
2007-05-28 17:41 ` Guy Harris
[not found] ` <465B144F.2070403-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
2007-05-28 17:58 ` Charles Clancy
[not found] ` <465B184C.1000306-VX+DGZyGJwM3uPMLIKxrzw@public.gmane.org>
2007-05-28 18:01 ` Johannes Berg
2007-05-28 18:15 ` David Young
2007-06-24 5:28 ` David Young
2007-05-28 18:00 ` Johannes Berg
2007-06-27 23:45 ` Guy Harris
[not found] ` <2A4D4978-D308-40EA-89D5-A2304A5947C7-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
2007-06-28 1:10 ` David Young [this message]
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=20070628011044.GD23293@che.ojctech.com \
--to=dyoung-e+axbwqsrlaavxtiumwx3w@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;
as well as URLs for NNTP newsgroup(s).