On Sat, 2010-10-02 at 05:19 +0200, Christian Lamparter wrote: > On Saturday 02 October 2010 04:56:35 Saqeb Akhter wrote: > > Nope I already noticed that 1.8.8.3 was available so to that step, I > > am getting frequent disconnects though, it might have to do with > > NetworkManager doing background scanning so going to try and it it to > > stop doing that. > Channel changes (especially with HT) are more expensive with AR9170 > than AR9271 which features "fastcc" (fast channel change). > > > The NetGear driver on windows seems to ignore the WMM requirement > > looks like. > You can actually peek into the Windows' driver logic. > The code is available under drivers/staging/otus/(80211core) > AFAIK, it only checks if the HT IEs are all present. > > > Either way that's what the problem was, going to see if i > > can get this disconnect problem sorted out. > I thought "the new" NetworkManager is more intelligent and > doesn't schedule scans while the device is actively > transmitting/receiving data. Anyway, NetworkManager is > "just" a manager for wpa_supplicant and wpa_supp works > well enough. NM >= 0.8.1 will request periodic scans unless you've locked the device to a specific BSSID, because if you've done this you are indicating that you don't need roaming. If you haven't specified a BSSID, then we still need periodic scans in case the device needs to roam between APs in a multi-AP system. Note that some drivers still appear to ignore BSSID locking. 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
