From: Helmut Schaa <hschaa@suse.de>
To: Jouni Malinen <j@w1.fi>
Cc: Holger Schurig <hs4233@mail.mn-solutions.de>,
linux-wireless@vger.kernel.org
Subject: Re: Pondering: how to improve mac80211 roaming ...
Date: Tue, 12 Aug 2008 14:40:23 +0200 [thread overview]
Message-ID: <200808121440.24098.hschaa@suse.de> (raw)
In-Reply-To: <20080812082246.GD4981@jm.kir.nu>
Am Dienstag, 12. August 2008 schrieb Jouni Malinen:
> On Tue, Aug 12, 2008 at 08:38:52AM +0200, Holger Schurig wrote:
> > In-kernel or in-userspace? --- or hybrid?
> > -------------------------------------------
>
> > So I think I'd opt to a hybrid approach. Userspace uses cfg80211
> > to configure some roaming threshold to mac80211. mac80211 would
> > gain AP-is-about-to-fail detection and, if it detects this, it
> > would signal via cfg80211 (is this possible?) to user-space that
> > it should now roam.
>
> I would also think that this is the most useful design. You could
> already do background scanning in the kernel (triggered by whatever) and
> just sen SIOCSIWSCAN WE event to notify user space (e.g.,
> wpa_supplicant) of availability of new scan results. This is something
> that madwifi for example is already doing.
JFYI I already started to rework the existing scan code in mac80211
(software scan) to do something like background scanning:
1) notify current AP about leaving the channel
2) scan one channel
3) get back to the operating channel
4) notify current AP about being back
5) back to 1) if more channels need to be scanned
The code basically works but is not cleaned up though and not yet triggered
by any event (just used the current start scan event to initiate a background
scan).
Maybe it is reasonable to use background scanning if the interface is
currently associated with an AP and regular scanning in all other cases.
Helmut
next prev parent reply other threads:[~2008-08-12 12:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 6:38 Pondering: how to improve mac80211 roaming Holger Schurig
2008-08-12 8:22 ` Jouni Malinen
2008-08-12 9:56 ` Holger Schurig
2008-08-12 12:40 ` Helmut Schaa [this message]
2008-08-12 15:42 ` Jouni Malinen
2008-08-12 17:56 ` Luis R. Rodriguez
2008-08-13 6:41 ` Holger Schurig
2008-08-13 6:50 ` Jouni Malinen
2008-08-13 12:26 ` Helmut Schaa
2008-08-13 12:49 ` Dan Williams
2008-08-13 12:53 ` Helmut Schaa
2008-08-13 14:18 ` Holger Schurig
2008-08-13 14:26 ` Helmut Schaa
2008-08-13 6:52 ` Holger Schurig
2008-08-13 12:02 ` Dan Williams
2008-08-13 14:28 ` Holger Schurig
2008-08-14 7:05 ` Kalle Valo
2008-08-14 8:25 ` Jouni Malinen
2008-08-14 18:30 ` Dan Williams
2008-08-14 6:42 ` Kalle Valo
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=200808121440.24098.hschaa@suse.de \
--to=hschaa@suse.de \
--cc=hs4233@mail.mn-solutions.de \
--cc=j@w1.fi \
--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).