From: Jean Tourrilhes <jt@hpl.hp.com>
To: Jouni Malinen <jkm@devicescape.com>
Cc: Dan Williams <dcbw@redhat.com>, Daniel Drake <dsd@gentoo.org>,
netdev@vger.kernel.org, softmac-dev@sipsolutions.net
Subject: Re: SIOCSIWESSID + SIOCSIWAP behaviour
Date: Mon, 15 May 2006 14:55:23 -0700 [thread overview]
Message-ID: <20060515215523.GA7570@bougret.hpl.hp.com> (raw)
In-Reply-To: <20060515214014.GA12019@instant802.com>
On Mon, May 15, 2006 at 02:40:14PM -0700, Jouni Malinen wrote:
> On Mon, May 15, 2006 at 01:28:13PM -0700, Jean Tourrilhes wrote:
>
> > I believe the BSSID has to be unique. HP APs can also offer
> > multiple ESSID for the same BSSID, but they do so using different
> > BSSID. If you look at the 802.11 spec, I can't see how two different
> > virtual cells can have the same BSSID, because the BSSID is the only
> > thing that identify the cell (the ESSID is not in each packet).
>
> What the standard says is somewhat irrelevant since there are APs that
> use multiple SSID with the same BSSID. I would say that it is reasonable
> for users to expect that this works with Linux, too.
Yeah, I guess it's required when you are using standard client
card, but using the same BSSID is not as clean.
> > Personally, I think that SIWAP is too tricky to use properly
> > for most users, so we should encourage them to not use it.
>
> Keep in mind that it is also used by some programs (e.g., wpa_supplicant
> in ap_scan=1) without the user having to know anything about that level
> of details..
My point is that we don't have to be perfect with respect to
the end user through SIWAP.
> > There is still a performance issue. Having to cancel and
> > restart associations waste CPU cycles. One way to deal with that would
> > be to improve the "commit" strategy of the Wireless API. Basically,
> > every time you do a set, you schedule or reschedule the "commit" ioctl
> > to happen in a few dozen ms. This way, you could bundle all the
> > settting of apps such as wpa_supplicant with only a single
> > commit. This is similar to the way the routing API works.
>
> Number of drivers use an atomic "associate" command (usually, a private
> ioctl) with wpa_supplicant. If there were a standard way of doing that,
> it could be helpful.
My goal was to offer the "commit" mechanism to solve those
issues. The basic plumbing is in place, so we just a slightly more
clever "commit" mechanism. The advantage is that the mechanism is
generic, so will work for anything.
> Jouni Malinen PGP id EFC895FA
Jean
prev parent reply other threads:[~2006-05-15 21:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-14 23:29 SIOCSIWESSID + SIOCSIWAP behaviour Daniel Drake
2006-05-15 3:29 ` Dan Williams
2006-05-15 13:16 ` Jouni Malinen
2006-05-15 14:19 ` Dan Williams
2006-05-15 20:28 ` Jean Tourrilhes
2006-05-15 21:40 ` Jouni Malinen
2006-05-15 21:55 ` Jean Tourrilhes [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=20060515215523.GA7570@bougret.hpl.hp.com \
--to=jt@hpl.hp.com \
--cc=dcbw@redhat.com \
--cc=dsd@gentoo.org \
--cc=jkm@devicescape.com \
--cc=netdev@vger.kernel.org \
--cc=softmac-dev@sipsolutions.net \
/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).