After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 649361 - Remember last network after wake-up
Remember last network after wake-up
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Dan Williams
Dan Williams
: 639323 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-05-04 10:33 UTC by Jendrik Seipp
Modified: 2012-12-20 15:05 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
log before suspend (5.94 KB, text/x-log)
2011-05-11 09:57 UTC, Jendrik Seipp 		Details
log after suspend (14.57 KB, text/x-log)
2011-05-11 09:59 UTC, Jendrik Seipp 		Details

Description Jendrik Seipp 2011-05-04 10:33:08 UTC 
This must have been reported earlier, but I can't find the bug.

It would be a great enhancement if NetworkManager would remember the last selected (wireless) network before suspend or hibernate is selected and if it could try to connect to that network automatically after the suspend.

Ideally the last selected VPN would be remembered as well.

If remembering the network is not feasible, a second option would be to be able to assign priorities to different networks.
Comment 1 Dan Williams 2011-05-06 18:05:59 UTC 
It should be doing this already, because NM uses "last connected network" as the best network to connect to, including after resume.  As long as the network that was previously connected to is still found in a scan, I'd expect NM to connect to it upon resume (also assuming you have that connection set to "connect automatically").  To debug this, can you grab logs of NM's operation across the suspend/resume from /var/log/messages (Fedora, SUSE) or /var/log/daemon.log (Debian, Ubuntu), whichever your distro uses?
Comment 2 Jendrik Seipp 2011-05-11 09:57:22 UTC 
Created attachment 187615 [details]
log before suspend
Comment 3 Jendrik Seipp 2011-05-11 09:58:51 UTC 
The two concerned networks are WLAN-unifr and VOIP-unifr. The network I connect to is WLAN-unifr. When I am connected and close and open the laptop's lid NetworkManager tries to connect to the other network VOIP-unifr. I have attached the log from /var/log/daemon.log split up into before and after closing the lid.
Comment 4 Jendrik Seipp 2011-05-11 09:59:23 UTC 
Created attachment 187616 [details]
log after suspend
Comment 5 Pavel Simerda 2012-07-26 11:41:53 UTC 
*** Bug 639323 has been marked as a duplicate of this bug. ***
Comment 6 Pavel Simerda 2012-07-26 11:43:01 UTC 
Is it still the case with current versions?
Comment 7 philippe-leon 2012-07-26 12:59:38 UTC 
I don't know (I'm the one who créated the duplicated bug), for now, the only remaining wifi in my neighbourhood is the "good" one.
Comment 8 Jiri Klimes 2012-07-26 13:23:59 UTC 
Jendrik, if you have still problem with connecting after resume, please follow instructions at https://live.gnome.org/NetworkManager/Debugging/#wifi and attach wpa_supplicant logs.

What Wi-Fi card do you have (lspci)? Are there any error regarding wlan0 in 'dmesg'?
Comment 9 Pavel Simerda 2012-08-16 20:34:40 UTC 
We lack information whether this bug still applies and how does it look like. Feel free to add information or file a new bug report.
Comment 10 Jendrik Seipp 2012-12-20 15:05:00 UTC 
It took a while for me to be able to test this. I think it has in fact been fixed by now.