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: Larry Finger <larry.finger@lwfinger.net>, Jouni Malinen <j@w1.fi>,
	wireless <linux-wireless@vger.kernel.org>
Subject: Re: RFC: ieee80211: Spamming of log resulting from packets with ExtIV  not set
Date: Sun, 8 Apr 2007 12:18:48 +0200	[thread overview]
Message-ID: <200704081218.49055.mb@bu3sch.de> (raw)
In-Reply-To: <1176019813.8459.15.camel@johannes.berg>

On Sunday 08 April 2007 10:10, Johannes Berg wrote:
> On Fri, 2007-04-06 at 23:16 -0500, Larry Finger wrote:
> 
> > As far as I can tell, FCS errors are not filtered.
> 
> Actually, they are filtered by the firmware and never passed up to the
> driver unless you set the "rx invalid frames" bit in the mac control
> field. Since the driver never sets that except with some of the module
> parameters (or is that modparm bcm43xx-mac80211 only?) the FCS on all
> frames passed up should be fine.

FCS corrupted frames are always filtered in bcm43xx. There's a
hack module parameter to pass them up in monitor mode in bcm43xx-mac80211.

-- 
Greetings Michael.

  reply	other threads:[~2007-04-08 10:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-06 23:53 RFC: ieee80211: Spamming of log resulting from packets with ExtIV not set Larry Finger
2007-04-07  1:38 ` Jouni Malinen
2007-04-07  4:16   ` Larry Finger
2007-04-07  4:33     ` Jouni Malinen
2007-04-07  7:56       ` Ulrich Kunitz
2007-04-08  8:10     ` Johannes Berg
2007-04-08 10:18       ` Michael Buesch [this message]
2007-04-08 14:09   ` Larry Finger

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=200704081218.49055.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --cc=larry.finger@lwfinger.net \
    --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).