linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Andy Green <andy@warmcat.com>, Jiri Benc <jbenc@suse.cz>,
	Daniel Drake <dsd@gentoo.org>,
	linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	kune@deine-taler.de
Subject: Re: [PATCH] zd1211rw-mac80211: Fix for monitor mode bug
Date: Wed, 28 Mar 2007 11:55:51 +0200	[thread overview]
Message-ID: <200703281155.52208.mb@bu3sch.de> (raw)
In-Reply-To: <1175073595.5151.28.camel@johannes.berg>

On Wednesday 28 March 2007 11:19, Johannes Berg wrote:
> On Mon, 2007-03-26 at 22:39 +0200, Michael Buesch wrote:
> 
> > Well, yeah. It does of course. If you have a STA and a MON interface,
> > the STA also receives the packs with bad CRCs. But that's how
> > mac80211 designed the virt-interface stuff.
> > Same goes for promisc. If you have a STA and a MON you can't have
> > the STA in non-promisc mode, so you also receive promisc packets on
> > the STA. That's how it's supposed to be. (I think mac80211 filters
> > them in the STA code somewhere).
> 
> Yeah, it filters those later by BSSID, that's intended, but it wasn't
> ever programmed to check the CRC. We'll need to introduce a new rx
> status flag "was crc checked".
> 
> > The modparams actually are just a temporary hack and were never meant
> > to stay there. I wanted to have the knob in cfg80211, sooner or later.
> > So when the knob is there, mac80211 should take care that the STA
> > doesn't receive the bad packets.

I think we need at least two "stages" for this config.
One that says: Get all packets with bad FCS
And one that says: Get all packets with bad FCS and everything else
that looks like a signal, which is probably your microwave oven, though.

So, when these packets are passed up the stack the PLCP is stripped.
I think we should make the stack aware of the PLCP (and add an RX flag
PLCP_available) so that it is able to check the PLCP checksum.
Otherwise the only way to detect your microwave oven from the packet
stream would be failed FCS. Which would also most likely failed then, but
I think it's probably useful for the user to see the PLCP, too, on
a mon interface.

So we need RX flags "PLCP_available" and "Not_checksummed".

-- 
Greetings Michael.

  reply	other threads:[~2007-03-28  9:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-25 23:18 [PATCH] zd1211rw-mac80211: Fix for monitor mode bug Daniel Drake
2007-03-26  9:54 ` Jiri Benc
2007-03-26  9:59   ` Johannes Berg
2007-03-26 10:14     ` Andy Green
2007-03-26 11:28       ` Michael Buesch
2007-03-26 11:31         ` Johannes Berg
2007-03-26 20:39           ` Michael Buesch
2007-03-28  9:19             ` Johannes Berg
2007-03-28  9:55               ` Michael Buesch [this message]
2007-03-28 10:18                 ` PLCP header information (was: Re: [PATCH] zd1211rw-mac80211: Fix for monitor mode bug) Johannes Berg
2007-03-26 10:28     ` [PATCH] zd1211rw-mac80211: Fix for monitor mode bug Johannes Berg

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=200703281155.52208.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=andy@warmcat.com \
    --cc=dsd@gentoo.org \
    --cc=jbenc@suse.cz \
    --cc=johannes@sipsolutions.net \
    --cc=kune@deine-taler.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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).