Description of problem: NetworkManager-openvpn cannot be configured to connect when advanced options are used in the config. many of the options are not available for configuration when defining a OpenVPN connection. in addition, importing a properly configured connection does not succeed, and many directives are not imported during the procoess.
Version-Release number of selected component (if applicable): 0.9.9.0
How reproducible: extremely reproducable
Steps to Reproduce:
1. create OpenVPN config:
keepalive 10 120
tls-auth tls-auth.key 1
2. attempt to import config created above
3. attempt to connect to OpenVPN
4. vi /etc/NetworkManager/system-connections/<name_given>
5. notice that many directives are not present
Actual results: OpenVPN connectivity does not work. several directives that are required for the connection are not present in the NetworkManager connnection configuration.
Expected results: NetworkManager would import all the settings, record all directives, and be able to establish a connection
step 1 should have the line "client" above "dev tap". copy/paste error missed that line.
Fedora (20) uses a NM-openvpn release that is close to upstream. Any change should be implemented upstream first.
Also, your request is quite generic. NM VPN plugins do not support arbitrary options, instead they must be thought every single one of them. Requests to blindly accept (openvpn) arguments were rejected in the past (e.g. https://bugzilla.gnome.org/show_bug.cgi?id=625247).
This is a known problem, especially for OpenVPN which has countless configuration options. Upstream will try to address this as https://bugzilla.gnome.org/show_bug.cgi?id=704866 .
So, there are two possibilities:
- somebody adds exactly the options you request to NM-openvpn. This is tedious, and I wouldn't hold my breath for that. (Patches welcome).
- upstream makes this simpler by solving bgo#704866. We hope to do that for NM v1.0, but probably it won't be backported to Fedora 20 -- only future Fedora releases.
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 20 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.