From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: radiotap-rN9S6JXhQ+WXmMXjJBpWqg@public.gmane.org
Subject: Re: Bad FCS flag
Date: Fri, 05 Sep 2008 22:44:08 +0200 [thread overview]
Message-ID: <1220647448.11109.26.camel@johannes.berg> (raw)
In-Reply-To: <20080905203839.GV29499-eZ+MEZF6i8Dc+919tysfdA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
> TCPDump uses this bit, too. I think that we are stuck with it.
Alright. I'll amend my old proposal to drop the shortGI bit for now (not
interested in 11n, let somebody else define those things) and make this
the "bad FCS" bit rather than the first bit in "RX flags".
> > * the unofficial RX-flags stuff defines that bit 0 in "RX flags" means
> > "bad FCS"
>
> Any users of this bit?
Not sure, I think we might create it in Linux, but it's easy to change.
> I think that TCPDump & Wireshark probably out-number the radiotap
> interpreters who use the rx-flags bit :-), but I don't know how many
> drivers there are who write headers with "bad FCS" in the rx flags bit.
Yeah. I'll mark the RX flags bit as reserved though so we don't run into
odd things there.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2008-09-05 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 20:25 Bad FCS flag Johannes Berg
[not found] ` <1220646325.11109.21.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2008-09-05 20:38 ` David Young
[not found] ` <20080905203839.GV29499-eZ+MEZF6i8Dc+919tysfdA@public.gmane.org>
2008-09-05 20:44 ` Johannes Berg [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=1220647448.11109.26.camel@johannes.berg \
--to=johannes-cdvu00un1vgdhxzaddlk8q@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 read-only IMAP folder(s) and NNTP newsgroup(s).