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 680955 - NetworkManager won't reconnect VPN after suspend, causing apps to connect through unsecure network
NetworkManager won't reconnect VPN after suspend, causing apps to connect thr...
Status: RESOLVED DUPLICATE of bug 349151
Product: NetworkManager
Classification: Platform
Component: VPN (general)
unspecified
Other Linux
: Normal major
: ---
Assigned To: Dan Williams
NetworkManager maintainer(s)
: 680956 680957 (view as bug list)
Depends on:
Blocks: nm-1.0
 
 
Reported: 2012-08-01 08:47 UTC by D.S. (Spider) Ljungmark
Modified: 2014-10-28 23:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description D.S. (Spider) Ljungmark 2012-08-01 08:47:31 UTC 
When connecting to the somewhat hostile conference Wifi, I always use a VPN tunnel (openvpn) set up through NetworkManager.

Currently, if I suspend the machine, by closing the lid, it will drop the Wifi and VPN connections.

If I resume the computer, by opening the lid and working again, it will reconnect to the _WIFI_ only, but not the VPN.


In a situation where you had WIFI + VPN setup previously, and reconnect to the _same_ wifi afterwards,  The network should not be considered "Ready" until the VPN is re-established.

The problem comes from applications such as Empathy, Epiphany and Firefox which are sending out information across the hostile network.
Comment 1 D.S. (Spider) Ljungmark 2012-08-01 09:03:02 UTC 
*** Bug 680956 has been marked as a duplicate of this bug. ***
Comment 2 D.S. (Spider) Ljungmark 2012-08-01 09:03:17 UTC 
*** Bug 680957 has been marked as a duplicate of this bug. ***
Comment 3 Pavel Simerda 2012-08-01 16:14:45 UTC 

*** This bug has been marked as a duplicate of bug 560471 ***
Comment 4 Pavel Simerda 2012-08-02 13:23:00 UTC 
Unduplicating and changing summary. Marking major as this can be viewed as a security issue that the user has no chance to prevent during wake up.
Comment 5 Pavel Simerda 2012-08-16 20:49:56 UTC 
Tightly related to bug 349151.
Comment 6 Dan Williams 2013-03-21 19:31:08 UTC 
One way to fix this with NM 0.9.8 is the new "secondary connection" support,where you can specify a VPN connection that should be started when your wifi connection (or any connection) is started.  If the VPN fails, then the entire connection will also fail.  This should fix the issue for your case, though it's not a blanket fix for always bringing up the VPN connection that was connected when we suspended.
Comment 7 Dan Winship 2013-05-02 16:04:58 UTC 
NM bugzilla reorganization... sorry for the bug spam.
Comment 8 Dan Williams 2014-05-05 22:25:54 UTC 
Moving this to 1.0 target to discuss whether anything needs to be done in addition to the "secondary connection" functionality that NM already has.
Comment 9 Dan Williams 2014-10-28 23:21:53 UTC 
Duping to bug 349151 because that contains the fixes for this too.

*** This bug has been marked as a duplicate of bug 349151 ***