Description of problem: In Fedora 18 we now have 2 ways to suspend the machine, through gnome-session (which sends out UPower dbus signals) or systemd (which sends out logind dbus singals). Systemd suspend takes place if you close the laptop lid or hit a keyboard shortcut. Unfortunately, because of this change some NM functionality got broken. When suspending, it doesn't disconnect from the network (I suppose it doesn't create a systemd inhibitor - delay lock). If I am connected to VPN and suspend and resume using systemd (laptop lid), it "seems" like I'm still connected to the VPN after resume. But in fact I'm not and my routing is completely broken. I have to disconnect from the VPN manually and reconnect again to have my network functional again. See: https://bugs.freedesktop.org/show_bug.cgi?id=58950 http://www.freedesktop.org/wiki/Software/systemd/inhibit Version-Release number of selected component (if applicable): NetworkManager-0.9.7.0-12.git20121004.fc18.x86_64 NetworkManager-pptp-0.9.3.997-3.fc18.x86_64 NetworkManager-vpnc-0.9.3.997-3.fc18.x86_64 NetworkManager-glib-0.9.7.0-12.git20121004.fc18.x86_64 NetworkManager-openconnect-0.9.7.0-1.git20120918.fc18.x86_64 NetworkManager-openvpn-0.9.3.997-3.fc18.x86_64 How reproducible: always Steps to Reproduce: 1. connect to wifi+VPN 2. suspend using systemd (laptop lid, keyboard shortcut) 3. resume 4. see that you're "still connected to VPN", but in fact the routing doesn't work
The systemd syspend/resume monitor was included into NM 2012-10-13: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=ea0c3a3e0fcbe400a704692d3b436d4733d348a1 But we have git20121004 snapshot in Fedora 18, so the functionality is not included. It will be present in NM 0.9.8 that should be released soon (next week).
gnome-session is using systemd as well
To clarify, this is not just about VPN. If I do systemd-controlled suspend (close the lid), the NM doesn't disconnect from the network and doesn't reconnect after resume. So if you move the laptop to a different place in the meantime, you seem to be still connected to the old wifi network - you have to manually reconnect. Also even if you stay in the same network, you might have IP address clashes if your IP address was assigned to someone else in the meantime. Can we please release the update soon?
NetworkManager-0.9.8.0-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/NetworkManager-0.9.8.0-1.fc18
Package NetworkManager-0.9.8.0-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing NetworkManager-0.9.8.0-1.fc18' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-3171/NetworkManager-0.9.8.0-1.fc18 then log in and leave karma (feedback).
NetworkManager-0.9.8.0-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.