linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jouni Malinen <j@w1.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Juuso Oikarinen <juuso.oikarinen@nokia.com>,
	linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	luciano.coelho@nokia.com
Subject: Re: [PATCH 0/2] mac80211: cfg80211: Roam trigger support
Date: Sun, 28 Mar 2010 15:48:29 -0700	[thread overview]
Message-ID: <20100328224829.GA22722@jm.kir.nu> (raw)
In-Reply-To: <20100328194332.GA384@jm.kir.nu>

On Sun, Mar 28, 2010 at 12:43:32PM -0700, Jouni Malinen wrote:
> On Wed, Mar 24, 2010 at 11:46:07PM -0700, Johannes Berg wrote:
> > So this is merged, anyone want to implement it in mac80211 so we can
> > start playing with it? I won't get around to it for quite a while.
> 
> How about something like this? Based on a very brief test (walk 10
> meters toward the AP and then back ;-) this seems to be doing more or
> less what I expect the feature should do.

And for those interested in playing more with this, I added support for
using the new signal strength threshold with the bgscan_simple module in
wpa_supplicant. This seemed to provide reasonable behavior in an office
environment with multiple APs and some overlapping coverage area in a
test with ath9k. I used following wpa_supplicant configuration option
for this particular test:
bgscan="simple:30:-50:300"

This uses background scan interval of 30 seconds if signal strength is
below -50 dBm and 300 seconds if above. A new scan is triggered
immediately if the signal strength drops below the threshold (or if it
drops further 4 dB and it has been more than 10 seconds from the
previous scan). Furthermore, I had manually configured the list of known
channels that the APs here are using (scan_freq parameter).

The connection did not die at any point (based on a continuous ping) and
roaming behavior seemed reasonable, i.e., signal strength did not drop
below -65 dBm or so before the new AP was already found. Background
scans are also quite tolerable when the frequency list is limited and
even more so, when remaining in the same location where the signal
strength remains above the threshold. That 300 second interval could
also be made much higher if it is desirable to avoid more or less all
background scans since the immediate scan triggered by signal strength
drop by itself should cover most use cases.

-- 
Jouni Malinen                                            PGP id EFC895FA

  reply	other threads:[~2010-03-28 22:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-23  7:02 [PATCH 0/2] mac80211: cfg80211: Roam trigger support Juuso Oikarinen
2010-03-23  7:02 ` [PATCH 1/2] cfg80211: Add connection quality monitoring support to nl80211 Juuso Oikarinen
2010-03-23 16:23   ` Luis R. Rodriguez
2010-03-24  6:14     ` Juuso Oikarinen
2010-03-24  6:54       ` Luis R. Rodriguez
2010-03-23  7:02 ` [PATCH 2/2] mac80211: Add support for connection quality monitoring Juuso Oikarinen
2010-03-23  7:13   ` Marcel Holtmann
2010-03-23  7:37     ` Juuso Oikarinen
2010-03-23 12:14       ` Marcel Holtmann
2010-03-23 13:20         ` John W. Linville
2010-03-23 16:21   ` Luis R. Rodriguez
2010-03-25  6:46 ` [PATCH 0/2] mac80211: cfg80211: Roam trigger support Johannes Berg
2010-03-28 19:43   ` Jouni Malinen
2010-03-28 22:48     ` Jouni Malinen [this message]
2010-03-29  6:27     ` Johannes Berg

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=20100328224829.GA22722@jm.kir.nu \
    --to=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --cc=juuso.oikarinen@nokia.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=luciano.coelho@nokia.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).