linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: jammy <benxuelan0402@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Lorenzo Bianconi <lorenzo.bianconi83@gmail.com>
Subject: Re: how can we fast roaming between multi-aps
Date: Mon, 29 Sep 2014 13:53:43 -0500	[thread overview]
Message-ID: <1412016823.4540.4.camel@dcbw.local> (raw)
In-Reply-To: <450E9BCC-651A-4ECF-8185-FCF5E7FD32A9@gmail.com>

On Sat, 2014-09-27 at 16:18 +0800, jammy wrote:
> Hi DAN,
> 1,Are all the SSIDs the same?
> A:yes,SSIDs are same.
> 2,What kind of authentication?  WPA Enterprise/802.1x?  What EAP methods?
> A:there are no authentication,and no EAP methods
> 3,Is pre-authentication enabled on the network and in the client?
> A:how to enable pre-authentication?My linux kernel is build by OpenWRT.
> 4,Is background scanning enabled in wpa_supplicant, and if so what is the interval?
> A:How to enable the background scanning in wpa_supplicant?

Given your answers, I think the problem is that background scanning is
not enabled in the supplicant.  The reason it's necessary for better
roaming is that when the signal from your current AP becomes weak, the
supplicant needs to know what AP to roam *to*.  It cannot do that unless
it has an up-to-date picture of the network, and what other APs it can
see.

Background scanning will initiate a scan when the current signal drops
below a certain threshold, so that when the current AP becomes unusable,
the supplicant can immediately switch to a better AP without delay.

If background scanning is not enabled, when the current AP goes out of
range the supplicant has to run a scan *after* it has disconnected,
which can take a few seconds.  That is likely the source of your issue.

In the supplicant configuration file, in the network block for your
SSID, put something like:

bgscan="simple:30:-45:300"

Dan


      reply	other threads:[~2014-09-29 18:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-20 18:26 compile Failed in openwrt for [PATCH] “add support for ack timeout estimation in ath9k driver ” jammy
2014-09-22 12:59 ` Lorenzo Bianconi
2014-09-26  2:37   ` jammy
2014-09-26  3:13   ` jammy
2014-09-26  3:22   ` how can we fast roaming between multi-aps jammy
2014-09-26 14:35     ` Dan Williams
2014-09-27  8:18       ` jammy
2014-09-29 18:53         ` Dan Williams [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=1412016823.4540.4.camel@dcbw.local \
    --to=dcbw@redhat.com \
    --cc=benxuelan0402@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo.bianconi83@gmail.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).