From: Jiri Benc <jbenc@suse.cz>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [WIP] mac80211: kill mgmt interface
Date: Thu, 21 Jun 2007 15:14:41 +0200 [thread overview]
Message-ID: <20070621151441.500d62d5@griffin.suse.cz> (raw)
In-Reply-To: <1182429920.21939.1.camel@johannes.berg>
On Thu, 21 Jun 2007 14:45:19 +0200, Johannes Berg wrote:
> On Thu, 2007-06-21 at 14:35 +0200, Jiri Benc wrote:
>
> > 1. I'm still not sure if using monitor interface for this purpose is a
> > good idea. Given the fact we want to switch to user space MLME, this
> > will mean that at least one monitor interface is always present. So we
> > got rid of management interface just to introduce another user visible
> > magic interface.
>
> Well, that's not a bad point, but at least it's not created via magic
> ioctls etc.
That's true. Still, couldn't we find a better solution?
I know that netlink isn't designed for this kind of things. But if we
don't have any other idea, I'd still prefer that over a dedicated
network interface.
> Actually, I first thought that as well, but in fact the userspace MLME
> in wpa_supplicant doesn't even need to connect these events, it simply
> checks which auth sequence number it sent and then assumes that whatever
> it did was correct and adds the sta to the associated/auth list on the
> callback.
If some program needs to get frames it injected back with a status,
there should exist an easy way to determine which status corresponds
with which frame. If there is no need to determine this, what is the
reason for returning back injected frames in the first place?
Jiri
--
Jiri Benc
SUSE Labs
next prev parent reply other threads:[~2007-06-21 13:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 9:42 [WIP] mac80211: kill mgmt interface Johannes Berg
2007-06-21 12:35 ` Jiri Benc
2007-06-21 12:45 ` Johannes Berg
2007-06-21 13:14 ` Jiri Benc [this message]
2007-06-21 23:27 ` Andy Green
2007-06-22 13:45 ` Jiri Benc
2007-06-22 14:29 ` Andy Green
2007-06-22 15:30 ` Johannes Berg
2007-06-22 15:49 ` Jiri Benc
2007-06-22 20:20 ` Johannes Berg
2007-06-23 5:58 ` Andy Green
2007-06-23 6:53 ` Johannes Berg
2007-06-23 9:00 ` Andy Green
2007-06-23 21:48 ` Johannes Berg
2007-06-24 8:51 ` Andy Green
2007-06-24 9:38 ` Johannes Berg
2007-06-23 11:44 ` Jiri Benc
2007-06-23 12:23 ` Andy Green
2007-06-23 21:51 ` Johannes Berg
2007-06-24 8:39 ` Andy Green
2007-06-24 10:46 ` Jiri Benc
2007-06-22 15:39 ` Jiri Benc
2007-06-22 17:00 ` Andy Green
2007-06-23 8:29 ` Andy Green
2007-06-23 21:41 ` Johannes Berg
2007-06-21 13:35 ` Jouni Malinen
2007-06-22 5:05 ` Michael Wu
2007-06-22 10:12 ` Johannes Berg
2007-06-23 7:08 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2007-06-21 21:50 Joerg Pommnitz
2007-06-22 9:10 ` Johannes Berg
2007-06-22 13:15 ` Jiri Benc
2007-07-01 1:48 ` Cohen, Guy
2007-07-02 13:38 AW: " Joerg Pommnitz
2007-07-02 13:53 ` Jiri Benc
2007-07-04 6:13 ` Tomas Winkler
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=20070621151441.500d62d5@griffin.suse.cz \
--to=jbenc@suse.cz \
--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