From: Jouni Malinen <jkmaline@cc.hut.fi>
To: jt@hpl.hp.com
Cc: Netdev <netdev@oss.sgi.com>,
hostap@shmoo.com, Linux Kernel <linux-kernel@vger.kernel.org>,
prism54-devel@prism54.org, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: Prism54 WPA Support - wpa_supplicant - Linux general wpa support
Date: Thu, 3 Jun 2004 19:33:03 -0700 [thread overview]
Message-ID: <20040604023303.GB7537@jm.kir.nu> (raw)
In-Reply-To: <20040603165233.GC8770@bougret.hpl.hp.com>
On Thu, Jun 03, 2004 at 09:52:33AM -0700, Jean Tourrilhes wrote:
> So, the plan would be to take Jouni's API as is (or with minor
> modifications) and stuff that in wireless.h. I don't believe that the
> tools themselves need to be modified, because wpa_supplicant is the
> sole user of those ioctls.
> If you are all happy with that, then I'll just do it.
I'm mostly happy with this, but this should also include something from
the private ioctls hostapd uses for AP functionality. In addition, I
would consider changing couple of text based elements (e.g., WPA IE as
hex string) to binary in order to remove extra parsing code and make the
data contents smaller. I'm having quite a bit of problems with scan
results getting too large for the current limit of 4 kB.. Admittedly,
this is in a test lab environment, but still, it is annoying and
requires workarounds like driver side filtering of the scan results.
I could try to make a list of all private ioctls currently used in
wpa_supplicant and hostapd, including some comments on what I would
consider changing at this point (mostly, changing text binary for couple
of cases and removing some fields that are not really going to be used).
Main categories for new functionality would be:
- key configuration (multiple algorithms, individual/unicast keys,
packet number set/get),
- WPA (or actually, generic) information element (get from scan results,
set for (Re)AssocReq/Beacon/ProbeResp)
- MLME requests (deauth/disassoc; maybe associate, too; I'm currently
using SIOCSIWAP for this; scan request with SSID (and maybe also
channel list) for active scanning
- authentication mode/encryption algorithm parameters (Host AP driver
does not current use this, but this is the way WPA drivers are used in
Windows NDIS and some Linux driver authors prefered this option and
wpa_supplicant supports it as an optional mechanism)
- some encryption related events/parameters (reporting Michael MIC
errors, TKIP countermeasures, configuration of "drop unencrypted" and
"privacy invoked").
Once we get some kind of testing version done, I will add a new driver
interface code for wpa_supplicant for the generic Linux wireless
extensions case and modify Host AP driver to use this. I hope that other
drivers would also start to use the new API at some point, although
wpa_supplicant is likely to maintain the backwards compatible interface
code for some time.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2004-06-04 2:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 7:14 Prism54 WPA Support - wpa_supplicant - Linux general wpa support Luis R. Rodriguez
2004-06-02 13:23 ` Jouni Malinen
2004-06-02 15:55 ` Luis R. Rodriguez
2004-06-03 1:40 ` Jouni Malinen
2004-06-03 2:38 ` Pedro Ramalhais
2004-06-03 3:44 ` Jouni Malinen
2004-06-03 11:05 ` Bradley Chapman
2004-06-03 16:52 ` Jean Tourrilhes
2004-06-04 2:33 ` Jouni Malinen [this message]
2004-06-04 18:01 ` Jean Tourrilhes
2004-06-03 4:06 ` Jeff Garzik
2004-06-03 17:07 ` Jean Tourrilhes
2004-06-02 16:28 ` Sam Leffler
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=20040604023303.GB7537@jm.kir.nu \
--to=jkmaline@cc.hut.fi \
--cc=hostap@shmoo.com \
--cc=jgarzik@pobox.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=prism54-devel@prism54.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).