Should setting a BSSID trigger a disconnection event from the driver? Obviously a disconnect event shouldn't be triggered if the BSSID being set is the same BSSID the card is already associated with. Or does that mean "reassociate unconditionally" ? But suppose we have two APs in the same ESS with obviously different BSSIDs. The card automatically associates with one BSSID, but wpa_supplicant decides it likes the other BSSID and calls SIOCSIWAP to lock to that one during the association process. Should the driver issue an IWAP event of 00:00:00:00:00:00 before attempting re-association with the BSSID that wpa_supplicant wants? The libertas driver currently does this; it sometimes confuses wpa_supplicant and is arguably wrong behavior because drivers don't issue disconnection events when auto-roaming from BSSID to BSSID in the same ESS. Conversely, if you have two access points 'linksys' with different BSSIDs that really _are_ two different ESSs, this would screw up userspace tools if a disconnect _wasn't_ sent. But in this case automatic tools have more problems than driver events. Thoughts? I guess I vote for not sending disconnect events if that BSSID has the same capabilities and the same SSID as the current association BSS. 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
