From: "Lars Ericsson" <Lars_Ericsson@telia.com>
To: "'John W. Linville'" <linville@tuxdriver.com>
Cc: "'Dan Williams'" <dcbw@redhat.com>,
"'Johannes Berg'" <johannes@sipsolutions.net>,
<hostap@lists.shmoo.com>,
"'Holger Schurig'" <hs4233@mail.mn-solutions.de>,
<linux-wireless@vger.kernel.org>
Subject: RE: Roaming problems
Date: Thu, 24 Apr 2008 11:55:52 +0200 [thread overview]
Message-ID: <009e01c8a5f1$625e0790$0b3ca8c0@gotws1589> (raw)
In-Reply-To: <200804240845.41867.hs4233@mail.mn-solutions.de>
> > I'm not disputing that as a reasonable approach. But FWIW for two
> > years we've been saying it is OK for drivers to use setting SSID as
> > the only trigger for association. Is that not your understanding?
>
Sorry, I din not know that there has been a discussion about the feature of
letting 'SSID set' trigger an association.
It's OK, but then the wpa_supplicant needs to 'cancel' current settings in
the driver before it start prepare for the new AP.
As I have understood it, that is done by issuing a BSSID of
00:00:00:00:00:00. I will look into a patch for that.
An other aspect of the selected design. If the driver (STA) is associated
with an BSSID and the wpa_supplicant would like to change BSSID, who is
responsible for a proper de- association/authentication from the first BSSID
?
My findings says that the network does not allow an STA to
associate/authenticate with one BSSID while it still have a valid aid with
an other BSSID. At least my Cisco AP does not allow that.
/Lars
next prev parent reply other threads:[~2008-04-24 9:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 15:09 Roaming problems Lars Ericsson
2008-04-23 8:39 ` Lars Ericsson
2008-04-23 11:12 ` Johannes Berg
2008-04-23 13:53 ` Dan Williams
2008-04-23 14:59 ` Johannes Berg
2008-04-23 16:21 ` Dan Williams
2008-04-23 16:39 ` Johannes Berg
2008-04-23 16:44 ` Lars Ericsson
2008-04-23 16:53 ` Johannes Berg
2008-04-23 17:12 ` Lars Ericsson
2008-04-23 17:59 ` Johannes Berg
2008-04-23 16:27 ` Lars Ericsson
2008-04-23 16:31 ` Dan Williams
2008-04-23 20:47 ` John W. Linville
2008-04-24 6:45 ` Holger Schurig
2008-04-24 9:55 ` Lars Ericsson [this message]
2008-04-24 9:59 ` Johannes Berg
2008-04-24 17:36 ` Lars Ericsson
2008-04-26 20:54 ` Johannes Berg
2008-04-28 18:28 ` Lars Ericsson
2008-04-28 18:34 ` Johannes Berg
2008-04-28 18:43 ` Dan Williams
2008-04-28 20:22 ` Lars Ericsson
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='009e01c8a5f1$625e0790$0b3ca8c0@gotws1589' \
--to=lars_ericsson@telia.com \
--cc=dcbw@redhat.com \
--cc=hostap@lists.shmoo.com \
--cc=hs4233@mail.mn-solutions.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).