From: Johannes Berg <johannes@sipsolutions.net>
To: Lars Ericsson <Lars_Ericsson@telia.com>
Cc: linux-wireless@vger.kernel.org
Subject: RE: Slow roaming in mac80211 (2.6.30).
Date: Thu, 23 Jul 2009 11:54:35 +0200 [thread overview]
Message-ID: <1248342875.19121.17.camel@johannes.local> (raw)
In-Reply-To: <2E12E93FA1AB41BDA5C8A7292FCAC884@gotws1589>
[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]
Lars,
> I have further investigated the roaming issues and found two problems.
Thanks!
> First ieee80211_rx_mgmt_deauth() and ieee80211_rx_mgmt_disassoc()
> sets a retry state at the same time as they tells the wpa_supplicant
> that the AP is gone.
>
> Patch lae-mac80211-rm-direct-probe.patch addresses this problem.
Hmm. I can see that being a problem, we might get away with just
removing the whole retry block. Ultimately though, I don't think it's a
-stable issue.
> Second problem address the auto scan function in
> ieee80211_sta_config_auth(). When an incomplete AP information is
> found, it start a new scan. This scan will delay the actions taken by
> the wpa_supplicant for the scan period.
>
> Patch lae-mac80211-rm-extra-scan-request.patch addresses this problem.
I don't think this is correct, it will only work properly with
wpa_supplicant I think. Not really sure though.
> > I would suggest you just use wpa_supplicant -Dnl80211, which
> > should help
> > a lot with this kind of things.
>
> I need to patch the kernel for this, rigth ?
> Where can I get appropriate patches?
No, you don't need to patch the kernel, you just need to use a git (?)
version of wpa_supplicant.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-07-23 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 21:21 Slow roaming in mac80211 (2.6.30) Lars Ericsson
2009-07-21 22:30 ` Johannes Berg
2009-07-23 9:40 ` Lars Ericsson
2009-07-23 9:54 ` Johannes Berg [this message]
2009-07-22 8:18 ` Lam Yoke Khei
2009-07-22 8:55 ` Holger Schurig
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=1248342875.19121.17.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=Lars_Ericsson@telia.com \
--cc=linux-wireless@vger.kernel.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