Comment 68 for bug 291760
Revision history for this message
| Howard Chu (hyc) wrote Re: network-manager roams to (none) ((none)) | #68 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
>> No. Opening the menu only shows you the results of the last scan, whenever that was. It doesn't initiate a scan.
>But the problem is that you cannot look in the menu to connect to a new AP because that list is outdated or non-existing.
>This feels kind of a regression to me.
The list will be outdated while you're currently connected to an AP. If you're disconnected, it will resume auto-scanning so it will get up to date "soon". So in general, if you've still got an active association, why do you need to choose a new AP from the menu?
If you have two APs available, you can measure how much lag you're going to get: keep one AP off, associate to the other. Then enable the second AP and disable the first. Then see how long it takes for the second AP to appear in the menu.
>Do we know that cards that are affected are affected on all APs or is that just a phenomenon we see on some APs? e.g. i remember that i saw a similar message like this in an office building at some point, but i never saw see it on my home AP.
I have a feeling it has to do with the number of APs returned in a scan, or more to the point, the length of time it takes to complete a scan.