Allow specifying an existing ovpn file instead of using the GUI for options

[Matt Lavin]

Like others in bug #364101, I have a .ovpn file that I can use to connect with the openvpn CLI, but I would prefer to use the GUI to manage my VPN connections. Rather than try to add support for every configuration option into the GUI, could the ability to use an existing .ovpn file be added instead?

If the openvpn client adds more features, they could be used immediately without waiting for a GUI update and people with working .ovpn files could easily use the GUI to manage their connections.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jan (jan-wiele)]

I also would like to have this feature, because some functions are not supported by the GUI, e.g., "ciper none".

[Stephan Fabel (sfabel)]

I've reported a similar problem under bug #1074261. I've marked it as duplicate of bug #364101 to consolidate and give the issue more traction. Seems like these problems are all inter-related and solving one of them would basically solve all three issues.

[epervieror (epervieror)]

As the openvpn server provide us already an .ovpn file, I would like to have this feature too.
Is there already ongoing work on this feature?

[Jazza (y-contact-ubntusso)]

Please add this, I beg it of you!

I've seen dozens and dozens of posts on the internet about problems that could have been avoided if people could just specify their original OVPN all because network manager doesn't support the custom configuration settings in the OVPN during import or through the GUI.

Even just a new variable for the VPN definition under /etc/NetworkManager/system-connections that network manager will just use when launching OpenVPN

Eg:
ovpn-file=client.ovpn

Please! Anything!

[Jazza (y-contact-ubntusso)]

Instead of just whining on a bug tracker I thought I'd take a look at source (trunk). Keep in mind, I don't develop linux software, don't have a linux build environment or version control setup, don't know how to package it, and don't know GTK so with all that in mind:

/src/nm-openvpn-service-defines.h
#define NM_OPENVPN_CONTYPE_OVPN_FILE "ovpn-file"

/src/nm-openvpn-service.c
Add in a new valid property in valid_properties[]
{ NM_OPENVPN_CONTYPE_OVPN_FILE, G_TYPE_STRING, 0, 0, FALSE }

/src/nm-openvpn-service.c under validate_connection_type function
Support NM_OPENVPN_CONTYPE_OVPN_FILE

/src/nm-openvpn-service.c under nm_openvpn_start_openvpn_binary function
Exclude tun default being added to openvpn arguments when specifying OVPN file.
Exclude reneg seconds default being added to openvpn arguments when specifying OVPN file.
Under connection type configuration, check for NM_OPENVPN_CONTYPE_OVPN_FILE and if used, verify specified OVPN file exists and add in the respective OpenVPN argument "--config myovpnfilepath.ovpn" else set error.

According to OpenVPN man page, --config can be mixed with other arguments so I'm guessing it'll still work with management socket, scripts, script security etc?

None of this touches on the UI/GTK stuff though.

[Jazza (y-contact-ubntusso)]

And support for NM_OPENVPN_KEY_OVPN_FILE as G_TYPE_STRING to specify the actual path to the file. This is why I don't code this myself :)

[Josef Kufner (jk-4)]

https://bugzilla.gnome.org/show_bug.cgi?id=625247 ... WONTFIX

[Dylan Powers (dylan-kyle-powers)]

I can import a ".ovpn" file with the "Import a saved VPN configuration..." under the connection types when adding a new network connection. Does that not provide the intended functionality everyone is looking for? This bug may be resolved now

[Jazza (y-contact-ubntusso)]

VPN Providers are using OVPN files more often because you can bundle the certificates and configuration into one file making them more relevant.

Last time I checked, the Import feature simply extracted supported values and loaded them into the application? The problem with that approach is OpenVPN is developed faster than network-manager-openvpn which means if network-m
anager-openvpn lags behind in supporting OpenVPN parameters, you're still left in a situation where you simply can't use it.
By simply specifying a OVPN file which is then just directly passed to OpenVPN as an argument without the same sort of processing, you can bypass this problem and enjoy the benefits of the UI and integration network-manager-openvpn brings.