On Sat, 2014-09-27 at 16:18 +0800, jammy wrote: > Hi DAN， > 1，Are all the SSIDs the same? > A：yes，SSIDs are same. > 2，What kind of authentication? WPA Enterprise/802.1x? What EAP methods? > A：there are no authentication，and no EAP methods > 3，Is pre-authentication enabled on the network and in the client? > A：how to enable pre-authentication？My linux kernel is build by OpenWRT. > 4，Is background scanning enabled in wpa_supplicant, and if so what is the interval? > A：How to enable the background scanning in wpa_supplicant？ Given your answers, I think the problem is that background scanning is not enabled in the supplicant. The reason it's necessary for better roaming is that when the signal from your current AP becomes weak, the supplicant needs to know what AP to roam *to*. It cannot do that unless it has an up-to-date picture of the network, and what other APs it can see. Background scanning will initiate a scan when the current signal drops below a certain threshold, so that when the current AP becomes unusable, the supplicant can immediately switch to a better AP without delay. If background scanning is not enabled, when the current AP goes out of range the supplicant has to run a scan *after* it has disconnected, which can take a few seconds. That is likely the source of your issue. In the supplicant configuration file, in the network block for your SSID, put something like: bgscan="simple:30:-45:300" 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
