> It turned out that, as a client, I don't have to bother with roaming stuff, it simply works out of the box. Roaming has 2 types: 1) based on the disconnection (beacon loss) 2) based on the RSSI Is it really roaming doing background scanning and preauth #2 (or) a connect and disconnect (assuming same ssid and security) #1? > Though, I have a couple of questions regarding this OOBX (new buzz word seen here and there for "out of the box experience" :) ). > - At which level the roaming is done? Is it at the WiFi kernel stack (cfg/mac 80211), at driver level, or at chipset/firmware level or a mix of them? > - Can I change my setup, so that I have control over the roaming? > - Is it a good idea to try to manage that myself from userspace? wpa_supplicant (userspace) takes care of the roaming for you, i belive it has support for both types #1 and #2 (along with background scan) Some proprietary version which implement at driver/fw level, this reduces the roam delay as it need not involve any context switches. -- 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
