On Wed, Apr 23, 2008 at 12:31:14PM -0400, Dan Williams wrote: > On Wed, 2008-04-23 at 18:27 +0200, Lars Ericsson wrote: > > The root problem is that the drive start associate when any of the > > ieee80211_ioctl_siwgenie() > > ieee80211_ioctl_siwessid() and ieee80211_ioctl_siwap() is called. > > If the wpa_supplicant need call more than one of them the association start > > to early. > > When either SIWESSID or SIWAP is called, the driver should restart > association using the latest settings sent by the supplicant. So by the > end of the GENIE -> SSID -> BSSID call chain, the driver should have > everything it needs to associate, and should restart association with > those parameters. I'm not disputing that as a reasonable approach. But FWIW for two years we've been saying it is OK for drivers to use setting SSID as the only trigger for association. Is that not your understanding? Clearly we need to get rolling on doing associations through nl80211... John -- John W. Linville linville@xxxxxxxxxxxxx -- 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
