From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Netdev <netdev@oss.sgi.com>,
hostap@shmoo.com, prism54-devel@prism54.org,
Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Prism54 WPA Support - wpa_supplicant - Linux general wpa support
Date: Fri, 4 Jun 2004 11:01:06 -0700 [thread overview]
Message-ID: <20040604180106.GA19181@bougret.hpl.hp.com> (raw)
In-Reply-To: <20040604023303.GB7537@jm.kir.nu>
On Thu, Jun 03, 2004 at 07:33:03PM -0700, Jouni Malinen wrote:
> 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.
Obviously we need the full functionality, not just some part
of it.
> 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.
The downside of that is that things need to be predefined. As
we are doing a "WPA API" and not a "generic link layer security API",
that's OK.
The other thing you may want to think about is miving all
string/arrays at the end of the definition so that we can grow them
easily if needed, and so that the first part can be fixed.
> 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.
That's easy to fix. I did the same with "iwpriv" definitions a
couple of weeks ago. Basically, you return -E2BIG to user space until
userspace give you a big enough buffer.
I'll try to fix that.
> 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).
You currently have your plate pretty full. I'll try to help,
but my first son was born one month ago and things are not as smooth
as planned.
> Jouni Malinen
Jean
next prev parent reply other threads:[~2004-06-04 18:01 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
2004-06-04 18:01 ` Jean Tourrilhes [this message]
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=20040604180106.GA19181@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--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).