I used NetworkManager Connection Editor to import OpenVPN, however, the connection did not work even though a lock icon is displayed and tun0 was created. Weird enough, there is not /var/log/NetworkManager file. Also, the /etc/openvpn folder was empty so I had to copy some file for testing. I tried to start the openvpn manually but that did not help
openvpn@NL.service - OpenVPN tunneling daemon instance using /etc/openvpn/NL.conf
Loaded: loaded (/usr/lib/systemd/system/openvpn@.service; enabled)
Active: inactive (dead)
nexus@linux:/etc/openvpn> sudo systemctl status openvpn@server.service
openvpn@server.service - OpenVPN tunneling daemon instance using /etc/openvpn/server.conf
Loaded: loaded (/usr/lib/systemd/system/openvpn@.service; enabled)
Active: failed (Result: exit-code) since Wed 2014-11-05 10:21:39 AST; 34min ago
Nov 05 10:21:39 linux.site openvpn[876]: Options error: In [CMD-LINE]:1: Error opening configuration file: server.conf
Nov 05 10:21:39 linux.site openvpn[876]: Use --help for more information.
Nov 05 10:21:39 linux.site systemd[1]: Failed to start OpenVPN tunneling daemon instance using /etc/openvpn/server.conf.
Could someone please help me to get openvpn work under 13.2 release?
Same issue as described above. Additionally I remember that on 13.1 tun0 was not created when connection was established.
When connecting manually via CLI the traffic is routed correctly, again via creating tun0 connection.
Also, when trying to Enable and Start the “openvpn@” service via Services Manager (Yast) and clicking OK to save the changes the following error is showed - “Could not enable openvpn@. Failed to get properties: Unit name openvpn@.service is not valid.”
I think in 13.1 the service was simply called “openvpn”. Could be the issue with the service package.
Any progress on resolving this issue (bug!). I tried installing manually the openvpn related packages (3 of them) from 13.1 distro, but no go. So, for now I am resolved to manually executing the VPN connection via CLI, of which I am getting tired … please help/assist on this matter, the only major one in 13.2 that I am unable to resolve or find solution for. As am using 95% wifi, “wicked” is no solution for me.
You cannot enable/start openvpn@.service. This is just a template.
You have to create a config in /etc/openvpn/ and then enable/start that particular instance.
E.g. if your config is named “vpn1.config”, use this:
If not a issue/bug then why when connectinf via NetworkManager the traffic is not being routed as per the VPN connection that gets established!
Of course this is not a design, rather something is wrong with some package. One doesn’t have to create a script manually, or config, that is why NetworkManager was designed in the first place, to automate connections, including the import files of vpn connections, one of them being the openvpn standard.
I am not sure about the 13.1, perhaps it was the same there and am wrong about the openvpn@.serive, but everything worked there by simply importing the .ovpn file and giving the authentication credentials, same thing as in CLI but rather via a GUI.
I don’t know. I never even used openvpn myself.
I was specifically talking about not being able to start openvpn@.service.
I have no idea at all how NetworkManager comes into play here anyway.
I am not sure about the 13.1, perhaps it was the same there and am wrong about the openvpn@.serive, but everything worked there by simply importing the .ovpn file and giving the authentication credentials.
Yes, it was the same in 13.1, that’s when openvpn was migrated from an old-style sysvinit script (/etc/init.d/openvpn) to a native systemd unit.
PS: I think there’s a misunderstanding here:
For creating a openvpn connection in NetworkManager, you do not have to enable/start an openvpn@xxx.service.
The service is for connecting at boot without network manager AIUI. Or maybe it is even the server part, not the client, I’m not sure.
I don’t use openvpn myself as mentioned, but a vpnc connection works fine here (setup in NetworkManager and nothing else).
Hmmmm … let me then try few more things, who knows, maybe we get lucky. Thanks for the input. We know that the openvpn protocol is working fine on 13.2, its just some issue with the NetworkManager and the openvpn plasma related files for it.
This package solves this long outstanding problem for past few months(!!). I am quite surprised that being it released late December it is still not available as updates for 13.2 and Tumbleweed.
Once added via Software Manager switch to using this repo and update all that system states, incl. dependencies/removals.
No more need to manually connect via CLI everytime.
me@linux-oi3d:~> ip route
default via 10.10.40.13 dev tun0 proto static metric 50
default via 192.168.1.1 dev wlp3s0 proto static metric 600
10.10.40.1 via 10.10.40.13 dev tun0 proto static metric 50
10.10.40.13 dev tun0 proto kernel scope link src 10.10.40.14
MY_EXTERNAL_IP via 192.168.1.1 dev wlp3s0 proto static metric 600
192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.4
192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.4 metric 600
Here, for the sake of some mindful purpose is the “ip route” output when connected via CLI:
me@linux-oi3d:~/Soft/VPN> ip route
0.0.0.0/1 via 10.10.40.13 dev tun0
default via 192.168.1.1 dev wlp3s0 proto static metric 600
10.10.40.1 via 10.10.40.13 dev tun0
10.10.40.13 dev tun0 proto kernel scope link src 10.10.40.14
MY_EXTERNAL_IP via 192.168.1.1 dev wlp3s0
128.0.0.0/1 via 10.10.40.13 dev tun0
192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.4
192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.4 metric 600
This package solves this long outstanding problem for past few months(!!). I am quite surprised that being it released late December it is still not available as updates for 13.2 and Tumbleweed.
Well, 1.0 is a major new version. There might be problems with other packages. E.g. I have no idea whether KDE4’s plasma-nm already supports NM 1.0. (and you didn’t mention which desktop you are using)
