From: Andy Green <andy@warmcat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Michael Wu <flamingice@sourmilk.net>, linux-wireless@vger.kernel.org
Subject: Re: Filtering in Monitor Mode (was Question about PRISM2 header rate field)
Date: Mon, 05 Mar 2007 13:46:41 +0000 [thread overview]
Message-ID: <45EC1F41.9070406@warmcat.com> (raw)
In-Reply-To: <1173100957.6131.76.camel@johannes.berg>
Johannes Berg wrote:
> The power save mode argument still holds though, we might address that
> with non-promisc monitor interfaces even though they do have a couple of
> problems (you need to be associated on a different virtual netdev for it
> to make sense...)
Hi Johannes -
Yes non-hardware promisc is an interesting combination for the userspace
MLME plan, since you have everything you need already without needing
hardware promisc. I guess the best way is to define a new MODE_ enum
for MONITOR_LOCAL or something.
-Andy
next prev parent reply other threads:[~2007-03-05 13:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 10:23 Question about PRISM2 header rate field Andy Green
2007-03-04 16:35 ` Andy Green
2007-03-05 0:15 ` Johannes Berg
2007-03-05 1:02 ` Andy Green
2007-03-05 3:10 ` Michael Wu
2007-03-05 8:10 ` Andy Green
2007-03-05 11:24 ` non-promisc monitor interfaces [was: Re: Question about PRISM2 header rate field] Johannes Berg
2007-03-05 11:34 ` Question about PRISM2 header rate field Johannes Berg
2007-03-05 13:00 ` Filtering in Monitor Mode (was Question about PRISM2 header rate field) Andy Green
2007-03-05 13:05 ` Johannes Berg
2007-03-05 13:18 ` Andy Green
2007-03-05 13:22 ` Johannes Berg
2007-03-05 13:46 ` Andy Green [this message]
2007-03-05 16:55 ` Question about PRISM2 header rate field Jouni Malinen
2007-03-05 20:39 ` Andy Green
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=45EC1F41.9070406@warmcat.com \
--to=andy@warmcat.com \
--cc=flamingice@sourmilk.net \
--cc=johannes@sipsolutions.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).