The problem with this is that if there are multiple ap with the same ssid and wep the client device may not chose to associate with the ap with the best signal. It has been requested to be able to list multiple ssid and multiple bssid to control how the client associates.
Add me to the list of requestees. We are upgrading some of our POPs to multiple base station radios. Seems like the clients (both aB series and aP(P) series in client bridge mode) when set to roaming (only setting ssid) will associate with the base station radio with best RSSI when the client is powered on. However, if you have to reset one of the APs then several of the clients will jump to the other AP (with lower signal) and will not jump back automatically when the first AP comes up again.
Seems like clients set to roaming will only start searching for the AP with best RSSI if the RSSI of the AP it is currently associated with drops below a certain roaming threshold (30-40%, I guess. A cursory glance through the documentation doesn't turn up the exact number).
How about this: - Client configuration is expanded to include a 'preferred bssid'. - Client will scan for the ssid, and will associate with the AP with the preferred bssid if available. - If not available, client will associate with the AP with same ssid and best RSSI. - If client is not currently associated with the AP with preferred bssid, it will scan for it on regular intervals (every 5 or 10 minutes, perhaps).
Even in it's current state it is great to be able to have two radio's on a pop and if one fails have the clients immediately switch to the other ap.
Definately. But I'd prefer it to switch back automagically when a radio with same ssid but with better signal strength comes back online.
-- LarsG
The PART-15.ORG smartBridges Discussion List
To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges <yournickname>
To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe smartBridges)
Archives: http://archives.part-15.org
