On Fri, 2009-01-09 at 09:55 +0200, Kalle Valo wrote: > Dan Williams <dcbw@xxxxxxxxxx> writes: > > >> Having the suspend scripts to tell NM to disconnect is just not a good > >> solution and especially in the embedded world this is a broken design > >> concept. > > > > Right; the missing piece is pushing the necessary roaming support down > > to the supplicant and letting it make the decisions about what to > > connect to. There's a few things that I need from the supplicant before > > I can simply push the entire config set down from NM and let it go wild: > > > > 1) A 'frequency' config item that works in infrastructure mode too, > > ignoring any AP not matching that frequency > > Just out of curiosity, why this feature is needed? I can understand > hard-coding bssid, but I don't understand the use for hard-coding the > frequency. If the user wishes to lock the connection to a specific frequency, irregardless of other values. Maybe you're right and we don't really care about it, but one other thing that would be nice is a "band" argument for a network block to differentiate A vs. B/G APs that might have the same SSID and security settings, but where the user only wants to use the A-side for example. Dan -- 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
