linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: further plan wrt. monitor interfaces
Date: Sun, 5 Aug 2007 11:29:23 +0200	[thread overview]
Message-ID: <200708051129.23301.IvDoorn@gmail.com> (raw)
In-Reply-To: <1ba2fa240708042358x6b206c4bla6f10589fd2cf97f@mail.gmail.com>

On Sunday 05 August 2007, Tomas Winkler wrote:
> On 8/4/07, Ivo van Doorn <ivdoorn@gmail.com> wrote:
> > Hi,
> >
> > >  * FIF_PROMISC_IN_BSS (BSS filters still on, but otherwise promisc)
> > >  * FIF_ALLMULTI               (all multicast frames are allowed through)
> > >  * FIF_BROADCAST      (broadcast frames are allowed through)
> > >  * FIF_FCSFAIL                (frames with bad FCS are allowed through)
> > >  * FIF_PLCPFAIL               (frames with bad PLCP checksum are allowed through)
> > >  * FIF_CONTROL                (control frames are shown)
> > >  * FIF_OTHER_BSS      (frames from other BSSes are shown, subject to the
> > >                        other filters)
> > > [missing anything?]
> >
> > rt2x00 registers have the 2 following entries as well:
> >
> >         Physical error
> >         Version error
> >
> >
> > The rest of the idea looks pretty good, si I will be happy to implement it for rt2x00. :)
> >
> > Ivo
> >
> >
> What about decryption error ?

those could be send to the mac80211 stack without the DECRYPTED flag set.
It will be up to mac80211 to take another shot at decrypting, send it further upstream as-is
or just simply drop it.

Ivo

  reply	other threads:[~2007-08-05  9:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-03 22:09 further plan wrt. monitor interfaces Johannes Berg
2007-08-03 22:14 ` Johannes Berg
2007-08-03 22:25 ` Johannes Berg
2007-08-03 22:35   ` Johannes Berg
2007-08-03 22:30 ` Johannes Berg
2007-08-03 22:56 ` Daniel Drake
2007-08-04  7:46   ` Ulrich Kunitz
2007-08-05 22:34     ` Daniel Drake
2007-08-06 10:11     ` Johannes Berg
2007-08-06 10:17     ` Johannes Berg
2007-08-06 21:23       ` Ulrich Kunitz
2007-08-07  9:46         ` Johannes Berg
2007-08-07 22:03           ` Ulrich Kunitz
2007-08-08  9:20             ` Johannes Berg
2007-08-04  7:59   ` Johannes Berg
2007-08-04  7:54 ` Andy Green
2007-08-04 11:22 ` Ivo van Doorn
2007-08-05  6:58   ` Tomas Winkler
2007-08-05  9:29     ` Ivo van Doorn [this message]
2007-08-06 10:09       ` 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=200708051129.23301.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tomasw@gmail.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).