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 -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
