Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Michael Wu <flamingice@sourmilk.net>, Jouni Malinen <j@w1.fi>,
	Zhu Yi <yi.zhu@intel.com>, Jiri Benc <jbenc@suse.cz>
Subject: Re: userspace MLME
Date: Fri, 08 Jun 2007 12:34:13 +0200	[thread overview]
Message-ID: <1181298853.6533.58.camel@johannes.berg> (raw)
In-Reply-To: <1181295319.6533.50.camel@johannes.berg>

[-- Attachment #1: Type: text/plain, Size: 926 bytes --]

On Fri, 2007-06-08 at 11:35 +0200, Johannes Berg wrote:

>  1) repost/integrate the injection patches

1b) do that filtering work we talked about
1c) implement the variety of monitor modes and that promisc bit
    passing through to drivers

> [1] Actually, I'd think that *all* commands should be forwarded to the
> userspace MLME except for commands *from* the userspace MLME. That way,
> the userspace MLME can act as a filter for commands which should make a
> whole bunch of things easier.

Ok so I just talked about this with Thomas Graf and Herbert Xu and
Herbert suggested that we solves the "single userspace MLME" only issue
in userspace. Then, we create a new multicast group for "userspace MLME"
that it signs up for. Then, we can use netlink_has_listeners to decide
whether there's a userspace MLME or not (we could even add a new command
"is userspace MLME present" based on that)

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

      reply	other threads:[~2007-06-08 10:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-08  9:35 userspace MLME Johannes Berg
2007-06-08 10:34 ` Johannes Berg [this message]

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=1181298853.6533.58.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=flamingice@sourmilk.net \
    --cc=j@w1.fi \
    --cc=jbenc@suse.cz \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=yi.zhu@intel.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