From: "Jouni Malinen" <jkm@devicescape.com>
To: Jiri Benc <jbenc@suse.cz>
Cc: "John W. Linville" <linville@tuxdriver.com>,
netdev@vger.kernel.org, jkmaline@cc.hut.fi
Subject: Re: [PATCH wireless-dev] d80211: Add support for user space client MLME
Date: Wed, 3 May 2006 09:44:58 -0700 [thread overview]
Message-ID: <20060503164458.GB10524@instant802.com> (raw)
In-Reply-To: <20060503182815.1a9ebb5e@griffin.suse.cz>
On Wed, May 03, 2006 at 06:28:15PM +0200, Jiri Benc wrote:
> It is too early for this. We need to implement some better communication
> interface between kernel and hostapd (or what will implement userspace
> MLME) first. The current solution, where there is some special
> net_device interface (wmaster0ap) abused to dump informations to
> userspace, is ugly and confusing for users.
Why do you think that this would be too early now? I agree that the
interface between kernel and user space MLME can be improved, but I see
no point in making client MLME implementation wait for that to happen.
Personally, I don't think that the wmaster#ap interface is really that
ugly, but I have nothing against this being improved if someone has time
for doing it. I just don't see it as the highest priority.
> There is no userspace MLME implementation yet. And if one is going to be
> written, I'm really convinced it should be written in a clean way. I
> think Simon said he would examine a possibility to convert this stuff to
> netlink - is there some progress there?
But there is.. I committed changes to the wpa_supplicant devel branch
for this yesterday. It seems to work fine with net/d80211 and bcm43xx
with this small patch to d80211 to allow the functionality to be moved
into user space.
I have not yet heard of anyone working with details of converting the
management frame communication to use netlink.
> Also, I'm not sure how fullmac cards could be (potentially) supported
> with this approach.
In the same way as with the kernel space MLME implementation.. This
does not really change regardless of where the MLME code is implemented.
Some time ago, I sent a preliminary patch showing what kind of changes
are needed and this was mainly avoiding calls to some ieee80211_sta.c
functions.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2006-05-03 16:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 21:18 [PATCH wireless-dev] d80211: Add support for user space client MLME Jouni Malinen
2006-05-03 16:28 ` Jiri Benc
2006-05-03 16:44 ` Jouni Malinen [this message]
2006-05-03 18:10 ` Jiri Benc
2006-05-03 18:35 ` Jouni Malinen
2006-05-04 9:00 ` Jiri Benc
2006-05-04 16:44 ` Jouni Malinen
2006-05-05 10:13 ` Johannes Berg
2006-05-05 13:17 ` [PATCH] d80211: switching management interface on/off Jiri Benc
2006-05-04 12:26 ` [PATCH wireless-dev] d80211: Add support for user space client MLME Johannes Berg
2006-05-10 17:17 ` [PATCH wireless-dev] d80211: Add support for user space clientMLME Jouni Malinen
2006-05-11 11:41 ` 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=20060503164458.GB10524@instant802.com \
--to=jkm@devicescape.com \
--cc=jbenc@suse.cz \
--cc=jkmaline@cc.hut.fi \
--cc=linville@tuxdriver.com \
--cc=netdev@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).