On Tue, Sep 28, 2010 at 08:17:04AM -0700, Ben Greear wrote: > On 09/28/2010 06:57 AM, Johannes Berg wrote: > >You can run all networks in a single wpa_s instance, I believe, and then > >it'd know about all this, right? > > But then, if you want to add an additional interface, you have to restart > everything. We would you restart everything? You can add/remove interface dynamically.. > I was thinking that maybe I could keep the logic in wpa_s, but instead of > all the special casing, just locate the current associated channel for the > phy in question and populate the scan-req with that single channel. wpa_supplicant already stores the operating channel: wpa_s->assoc_freq. You can iterate over the configured interfaces and fetch the current operating channel(s) using that without adding anything new to the kernel. With that, you could make some wpa_supplicant scans (e.g., bgscan or scan for new networks if only a single network block is enabled) restrict the list of channels to scan. Still, some other scan requests (e.g., user initiated full scan or P2P Search) would need to be able to specify more channels even if one of the interfaces is associated. I would like to get rid of the one-channel-per-phy restriction, so I don't think I would like to see new code added for that. -- Jouni Malinen PGP id EFC895FA -- 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
