From: "Lars Ericsson" <Lars_Ericsson@telia.com>
To: "'Johannes Berg'" <johannes@sipsolutions.net>
Cc: "'John W. Linville'" <linville@tuxdriver.com>,
"'Dan Williams'" <dcbw@redhat.com>,
"'Holger Schurig'" <hs4233@mail.mn-solutions.de>,
<linux-wireless@vger.kernel.org>
Subject: RE: Roaming problems
Date: Mon, 28 Apr 2008 22:22:42 +0200 [thread overview]
Message-ID: <00ab01c8a96d$9d9360b0$0b3ca8c0@gotws1589> (raw)
In-Reply-To: <1209407657.29025.21.camel@johannes.berg>
> That would be doable as well (though I would argue it should
> be done in addition), we could use Holger's approach and
> delay the actual association sequence start until a commit
> wext ioctl is received or a timer expires. Then
> wpa_supplicant can call the commit explicitly after doing everything.
Yes I like this. A commit ioctl issued from the wpa_supplicant when all
configuration is done is the preferred solution.
The commit ioctl that will speed up the roaming and the timer that will trig
the association if no commit ioctl is received which gives backwards
compatibility.
But, we then need to change the current implementation where 3 ioctls trigs
an immediate association start.
/Lars
prev parent reply other threads:[~2008-04-28 20:23 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
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 [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='00ab01c8a96d$9d9360b0$0b3ca8c0@gotws1589' \
--to=lars_ericsson@telia.com \
--cc=dcbw@redhat.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).