From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: David Seira <davidseira@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Roaming behavior
Date: Wed, 12 Aug 2009 09:07:18 +0200 [thread overview]
Message-ID: <200908120907.18501.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <1250003481.4185.7.camel@solid2>
> I want to delete this behavior because I'm developing an
> application which do that alone.
Please look at wpa_supplicants behavior when you configure
ap_scan= and scan_ssid=. With them, you can configure
wpa_supplicant to not issue scan requests on it's own.
Then your user-space app can do the monitoring, scanning (via
nl80211) issue a command to wpa_supplicant to authenticate to
some AP.
Another option would be to look into network-manager and see what
it offers.
But basically, mac80211 has inferior support for roaming compared
to some older solutions.
Some examples: with madwifi, I can tell the driver to only scan
on channels 1,6,11. That's not exactly standards-conforming, but
can speed up roaming considerably, because a full scan is now
way shorter. mac80211 doesn't support such a thing directly. It
just occurs to me that you might be able to do something like
with with a special regulatory daemon.
Or with orinoco, you could define a level when to roam (e.g. at
what SNR/RSSI/whatever it is based on). mac80211 doesn't have
this.
I'm quite sure that this will be eventually done, and then you
have the same seamless roaming with all/most of your WLAN cards,
where with the pre-mac80211 only some of the card did somewhat
well and other cards were only usable for hot-spot operation.
--
http://www.holgerschurig.de
next prev parent reply other threads:[~2009-08-12 7:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 12:44 Roaming behavior David Seira
2009-08-11 13:59 ` John W. Linville
2009-08-11 15:11 ` David Seira
2009-08-12 7:07 ` Holger Schurig [this message]
2009-08-12 7:14 ` Johannes Berg
2009-08-13 9:44 ` David Seira
2009-08-13 17:20 ` Dan Williams
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=200908120907.18501.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=davidseira@gmail.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;
as well as URLs for NNTP newsgroup(s).