From: Andy Green <andy@warmcat.com>
To: linux-wireless@vger.kernel.org
Subject: Question about PRISM2 header rate field
Date: Sun, 04 Mar 2007 10:23:53 +0000 [thread overview]
Message-ID: <45EA9E39.6080706@warmcat.com> (raw)
Hi folks -
I can decode captured Monitor Mode PRISM2 headers in a reasonable way,
except for the rate field.
On a capture of a broadcast which I believe was at 54Mbps, I see the
PRISM2 / ieee80211_frame_info field "datarate" is set to 0xf0, or 240
decimal. I looked around at the various different ways of talking about
tx rate in the stack and drivers, but none that I found use 0xf0 for
54Mbps. Is it 48Mbps in units of 200kHz? Or 54Mbps in units of 225kHz
(!!) Or...?
I am trying to reissue this captured packet using the management
interface (which I can now conjure up) with a rate that I can control,
but I did not find any information on the coding for this field.
-Andy
next reply other threads:[~2007-03-04 10:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 10:23 Andy Green [this message]
2007-03-04 16:35 ` Question about PRISM2 header rate field Andy Green
2007-03-05 0:15 ` Johannes Berg
2007-03-05 1:02 ` Andy Green
2007-03-05 3:10 ` Michael Wu
2007-03-05 8:10 ` Andy Green
2007-03-05 11:24 ` non-promisc monitor interfaces [was: Re: Question about PRISM2 header rate field] Johannes Berg
2007-03-05 11:34 ` Question about PRISM2 header rate field Johannes Berg
2007-03-05 13:00 ` Filtering in Monitor Mode (was Question about PRISM2 header rate field) Andy Green
2007-03-05 13:05 ` Johannes Berg
2007-03-05 13:18 ` Andy Green
2007-03-05 13:22 ` Johannes Berg
2007-03-05 13:46 ` Andy Green
2007-03-05 16:55 ` Question about PRISM2 header rate field Jouni Malinen
2007-03-05 20:39 ` Andy Green
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=45EA9E39.6080706@warmcat.com \
--to=andy@warmcat.com \
--cc=linux-wireless@vger.kernel.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).