I have configured two openvpn connections in NetworkManager. Both work if I start/stop them with NM. But if I try to start the second openvpn when the first is running, both disconnect. I have tried to put different names to the tun devices (tun1, tun2) but I doesn't change the outcome. Packages: NetworkManager-openvpn-gnome-1.0.0-1.fc21.1.x86_64 NetworkManager-openvpn-1.0.0-1.fc21.1.x86_64 openvpn-2.3.6-1.fc21.x86_64 These are the logs I get when I activate the second openvpn connection dbus[1183]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' NetworkManager[1278]: nm-openvpn-Message: Terminated openvpn daemon with PID 43625. NetworkManager[1278]: <error> [1426679270.748466] [platform/nm-linux-platform.c:2266] link_change(): Netlink error changing link 16: <DOWN> mtu 0 (1) driver 'unknown' udi '/sys/devices/virtual/net/tun2': No such device NetworkManager[1278]: <error> [1426679270.748709] [platform/nm-linux-platform.c:1782] delete_object(): Netlink error deleting 10.76.54.5/24 lft forever pref forever lifetime 92323-0[4294967295,4294967295] dev tun2 src kernel: No such device (-31) NetworkManager[1278]: <info> VPN plugin state changed: stopping (5) NetworkManager[1278]: <info> VPN plugin state changed: stopped (6) NetworkManager[1278]: <info> VPN plugin state change reason: unknown (0) NetworkManager[1278]: <warn> error disconnecting VPN: Could not process the request because no VPN connection was active. NetworkManager[1278]: <info> (tun2): device state change: activated -> unmanaged (reason 'removed') [100 10 36] NetworkManager[1278]: <info> (tun2): deactivating device (reason 'removed') [36] dbus[1183]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' nm-dispatcher[43766]: Dispatching action 'vpn-down' for tun2 nm-openvpn[43625]: SIGTERM[hard,] received, process exiting
The upstream bug is 7 years old, cool!
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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' of '21'. 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 21 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.
The same happens in Fedora 22
NetworkManager-openvpn-1.2.4-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-c719a6115b
NetworkManager-openvpn-1.2.4-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-c719a6115b
NetworkManager-openvpn-1.2.4-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.