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 793801 - Option to automatically connect to VPN
Option to automatically connect to VPN
Status: RESOLVED DUPLICATE of bug 672400
Product: gnome-control-center
Classification: Core
Component: Network
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2018-02-25 00:02 UTC by Daniel B
Modified: 2018-02-25 00:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Daniel B 2018-02-25 00:02:21 UTC
For years now, I have been waiting for the network settings in gnome to become complete. At first I thought that it was incomplete because it was new, but it has been so long now that I think that maybe someone forgot about it. 

Network Manager's "nm-connection-editor" has a section in the "Generel" tab when editing network devices like a Lan or WiFi connection, which is called "Automatically connect to VPN...". It allows you to specify a specific VPN connection to use with that particular network connection and have it automatically connect to the VPN whenever the network connection has been established. 

This option has always, and still is to this day, missing when editing connections from gnomes network settings. I don't see much point in having a custom connection editor in gnome, when you always have to open the network manager version to complete the setup. 

So it would be nice if this could either be implemented soon, or instead simply drop the custom editor and just integrade nm-connection-editor back into gnome. Either way, a single editor should be enough.
Comment 1 Piotr Drąg 2018-02-25 00:39:44 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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