View Full Version : Roaming
Hi,
does anyone have some experience with wifi clients roaming between WL500b(g) access points? I would like to know if it works without problems etc. Example setup: 6 WL500b(g) APs, 10 mobile CISCO 350 clients roaming between these 6 APs.(one IP subnet, not overlaping channels etc, good coverage etc.) We have experienced and tried like 5 different AP vendors, and we have had a problems like disconnection issues etc due to "bad" roaming between APs. I don't know how behave Broadcom chipsets included in WL500b(g). Any suggestions, experince would be helpful and really appriciated. Thank you all for your answers.
Hi,
does anyone have some experience with wifi clients roaming between WL500b(g) access points? I would like to know if it works without problems etc. Example setup: 6 WL500b(g) APs, 10 mobile CISCO 350 clients roaming between these 6 APs.(one IP subnet, not overlaping channels etc, good coverage etc.) We have experienced and tried like 5 different AP vendors, and we have had a problems like disconnection issues etc due to "bad" roaming between APs. I don't know how behave Broadcom chipsets included in WL500b(g). Any suggestions, experince would be helpful and really appriciated. Thank you all for your answers.
Well, there should not be any problem with WL500b/g regarding to roaming. You can even tune up roaming parameters using the wl options:
roam_trigger # Set the roam trigger RSSI threshold. (integer)
roam_delta # Set the roam candidate qualification delta. (integer)
roam_scan_period # Set the roam candidate qualification delta. (integer)
I am not sure if these parameters are not valid in Client mode only because the Client itself must decide when to switch to another AP. You should setup the RSSI treshold properly. I would say that your problem lies in bad configuration of CISCO clients (try to upgrade firmware if available) and replacement of APs will NOT help you a lot...
Well, there should not be any problem with WL500b/g regarding to roaming. You can even tune up roaming parameters using the wl options:
roam_trigger # Set the roam trigger RSSI threshold. (integer)
roam_delta # Set the roam candidate qualification delta. (integer)
roam_scan_period # Set the roam candidate qualification delta. (integer)
I am not sure if these parameters are not valid in Client mode only because the Client itself must decide when to switch to another AP. You should setup the RSSI treshold properly. I would say that your problem lies in bad configuration of CISCO clients (try to upgrade firmware if available) and replacement of APs will NOT help you a lot...
I've tried to upgrade/downgrade firmware, but it doesn't improved anything regarding this problem. I've also tried a card with PRISM chipset, but it behave same. Anyway I'll try to play more with settings you've recommended and I'll see. Thanks