Description of problem: (This is a repeat of really old behavior) I suspend @ work, while my laptop is connected to the wireless network there. I resume @ home. Instead of rescanning and connecting to my home network, it spins trying to reconnect to the work network (which doesn't exist here.) In fact, after manually selecting my home network, it then two minutes later dropped the connection and tried to reconnect to the work wireless. Version-Release number of selected component (if applicable): NetworkManager-0.8.1-6.git20100831.fc14.x86_64 How reproducible: 100% so far Steps to Reproduce: 1. suspend @ work 2. resume @ home Actual results: Connects to wrong wireless network (or, at least, tries to.) Expected results: Connects to right network
It seems that NetworkManager can not reactivate network after standby, although resume from hibernation works. Confirmed here with Fedora 13.
Bill, can you reproduce the described behaviour? If yes, please provide the output of grep NetworkManger /var/log/messages Maybe it is a duplication of bug #630381.
Take a look to my comment #10 to bug #627365. The workaround there works for me to fix the issue.
Raphael - I provided the logs out of band. Sorry about any confusion.
I see this exact same issue on up-to-date F16. However, here, it's worse. I'm suspending and resuming, but not actually moving - so NM should reconnect back to the network which was previously connected. Instead, it tries to connect to another wifi network, for which I don't have keys.
(In reply to comment #6) Well, wireless connection are stateless due to technical restrictions. And time elapses while you hibernate, so the chance that parameters change are really high. So, the solution is only to disable wlan completely before hibernating. Resume can enable it again and do a completely fresh (re-)connect to the preferred wifi. Ergo, unsure if it is really a bug at all.
This is pretty clearly a bug where I'm sitting: NetworkManager is attempting to connect to a network I've never asked it, or given it permission to, connect to. If I had open networks here, I'd be wondering if it would connect to one of those seemingly at random? That could be a pretty serious security bug if so, because there would be no UI to indicate that it had connected to a network it had never been asked to connect to. I've no idea what the solution is, to but say it's not a bug because of some hardware restriction is missing the point: the behaviour is buggy.
(In reply to comment #8) > This is pretty clearly a bug where I'm sitting: NetworkManager is attempting to > connect to a network I've never asked it, or given it permission to, connect > to. NM won't auto-connect to networks for which it has no connection profile or the profile is not marked for automatic connection. The profiles for unwanted networks could be created due to a GnomeShell bug: https://bugzilla.gnome.org/show_bug.cgi?id=650494#c8 You can list all connection like this: $ nmcli -f all con See also bug 717665
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping