Hi Jean,
I'd just like to check my understanding (and softmacs implementation)
of SIWESSID and SIWAP behaviour, for managed mode.
When SIWESSID happens, softmac drops association/authentication with the
current network and then starts a scan for the requested SSID. When
found, softmac authenticates and associates to that network.
When SIWAP happens, softmac drops association/authentication with the
current network and then starts a scan for the requested BSSID. When
found, softmac authenticates and associates to that network.
Is it correct that both of these immediately trigger
deauthenication+deassocation then authentication+assocation?
Is it correct that SIWAP can legally select *any* AP? (As opposed to
only being for selecting a specific AP *on the ESS* indicated by a past
or future SIWESSID call)
Right now, wpa_supplicant does SIWESSID and SIWAP in quick succession,
which causes softmac to associate twice, and that quickly confuses things.
No matter how I think of it, this strikes me as a hard interface to
implement. Because association isn't an atomic operation, it is tricky
to get the sequencing right, e.g. if the user does SIWESSID to start
association, and then SIWAP to select a different AP before the original
association has completed.
Any clarification appreciated.
Thanks,
Daniel
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
