Ubuntu
network-manager package

  1. Bug #291062
  2. Comment #47

Comment 47 for bug 291062

Revision history for this message
Michael Doube (michael-doube) wrote :

I've tried 55NetworkManager script (https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/291062/comments/34) on a Hardy installation, with interesting results:

If I haven't moved during a suspend-resume cycle, I get wifi back quickly, as my notebook remains associated with my home AP. But if I suspend at home (homeAP) then go to work (workAP; 1 hour away on the Tube), I resume and am still 'associated' with homeAP. To get workAP to show up in NM's list and to associate with workAP, I have to R-click->disable wireless and enable wireless. homeAP is still in the list for a couple of minutes.

So it seems that the behaviour is to assume that if we were associated with an AP at suspend then we are still associated at resume. Perhaps that is fair, but it would be worth doing an AP scan soon after resume to check if this is true, and if not, associate with an AP that is actually there.