On Mon, Feb 14, 2011 at 4:12 PM, John W. Linville <linville@xxxxxxxxxx> wrote: > Neither -- the driver (like all mac80211-based drivers) simply does > not support that setting. mac80211-based drivers are simple, and > they don't do roaming by themselves. Instead they rely on a userland > component (e.g. wpa_supplicant) to take care of roaming for them. > > Unfortunately, I don't know of any roaming "knobs" to turn for > wpa_supplicant (or NetworkManager) -- maybe it would be nice to > have one. Even if it were there, I suspect that control of that > "knob" would have to flow through NetworkManager if you are using it. > > John Yes I eventually homed in on the reality that you just described. I was able to get an ipw2200 based laptop to roam nicely as the driver did support the sens parameter - and it did switch over to another AP when the signal from the first went near non-existent - which was what I was after. However it seems that using my netbook with an ath5k driver based wireless internal simply won't be able to do it whatever I do - is there anyone working to make mac80211 drivers more sophisticated in the future? Maybe roaming is not high on most user's agenda? But the main, and separate, issue I have is with initial selection of a weak AP signal when a strong one (with same ssid) seems more logical - and I don't know if this is something that is within the realm of the driver, the NM code or wpa_supplicant? I am not sufficiently knowledgeable to know what is possible here. I would certainly appreciate knowing what is possible, and what provides the limitations? -- mike c -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
