From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: radiotap <radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org>
Subject: [UPDATE] RX flags
Date: Fri, 13 Mar 2009 12:43:30 +0100 [thread overview]
Message-ID: <1236944610.5235.32.camel@johannes.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
Since there were no objections, we have adopted the following radiotap
changes:
1) Add the "bad FCS" flag to the flags field (field 1) with the bit
number 6, i.e. mask 0x40. [1]
2) Define the new RX flags field at field number 14, with the following
definition:
- field contents: a single 16-bit integer
- field alignment: 2
- define bit 0 (mask 0x0001) to be reserved (it was defined by some
implementations as "bad FCS" which is in the flags field)
- define bit 1 (mask 0x0002) of this field to mean "frame has bad
PLCP"
- all other bits (mask 0xfffc) shall be reserved for future
assignment
I will take care to update the Linux implementation, any pointers on
where to send the wireshark patch would be appreciated.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2009-03-13 11:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1236944610.5235.32.camel@johannes.local \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=radiotap-sUITvd46vNxg9hUCZPvPmw@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 read-only IMAP folder(s) and NNTP newsgroup(s).