From: Andy Green <andy@warmcat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Tomas Winkler <tomasw@gmail.com>,
Simon Barber <simon@devicescape.com>,
Michael Wu <flamingice@sourmilk.net>,
mabbas <mabbas@linux.intel.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
Jouni Malinen <jkm@devicescape.com>
Subject: Re: [patch 2/5] Add basic support for IEEE 802.11n discovery and association
Date: Thu, 12 Apr 2007 10:01:58 +0100 [thread overview]
Message-ID: <461DF586.6050009@warmcat.com> (raw)
In-Reply-To: <1176368209.7052.10.camel@johannes.berg>
Johannes Berg wrote:
> On Thu, 2007-04-12 at 00:25 +0100, Andy Green wrote:
>
>> Since hopefully the concept will involve a kernelside-filtered
>> monitoring action via libpcap, the stack could for example inject a
>> periodic stats summary packet down the monitor interface back to userspace.
>
> Eek. No *new* fake packets any more please.
Just curious, why is that evil? It seems if the usermode MLME is
interested in what are basically Out Of Band 1Mbps management packets
that share the same air as the payload packets and so appear on Monitor
mode interfaces, then a local OOB class of packet doesn't break such new
ground. And it does neatly fit the communication semantic already used.
-Andy
next prev parent reply other threads:[~2007-04-12 9:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 11:38 [patch 2/5] Add basic support for IEEE 802.11n discovery and association mohamed
2007-03-26 23:52 ` Randy Dunlap
2007-04-04 10:37 ` mabbas
2007-03-27 17:05 ` Luis R. Rodriguez
2007-03-27 17:11 ` Luis R. Rodriguez
2007-03-27 17:29 ` Luis R. Rodriguez
2007-03-29 6:04 ` mohamed
2007-03-28 19:11 ` Luis R. Rodriguez
2007-03-29 7:21 ` mohamed
2007-03-28 9:14 ` Johannes Berg
2007-03-29 5:56 ` mohamed
2007-03-28 20:03 ` Johannes Berg
2007-03-29 19:46 ` Luis R. Rodriguez
[not found] ` <1ba2fa240703291648h6b0d10bdje2ea54f3c1754f5b@mail.gmail.com>
2007-03-30 10:38 ` Johannes Berg
[not found] ` <1ba2fa240703300418r781931cdp50430dcb02259f1@mail.gmail.com>
2007-03-30 12:11 ` Johannes Berg
2007-03-31 15:37 ` Michael Wu
2007-04-11 19:40 ` John W. Linville
2007-04-11 20:04 ` mabbas
2007-04-11 20:29 ` Michael Wu
2007-04-11 22:03 ` Tomas Winkler
2007-04-11 22:50 ` Simon Barber
2007-04-11 23:05 ` Tomas Winkler
2007-04-11 23:25 ` Andy Green
2007-04-12 8:56 ` Johannes Berg
2007-04-12 9:01 ` Andy Green [this message]
2007-04-12 9:06 ` Johannes Berg
2007-04-12 0:20 ` Simon Barber
2007-04-12 1:13 ` Tomas Winkler
2007-04-11 22:23 ` mabbas
2007-04-11 22:56 ` Michael Wu
2007-04-12 18:11 ` mabbas
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=461DF586.6050009@warmcat.com \
--to=andy@warmcat.com \
--cc=flamingice@sourmilk.net \
--cc=jkm@devicescape.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mabbas@linux.intel.com \
--cc=simon@devicescape.com \
--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).