Openvpn on ubuntuMATE?

Support & Help Requests
1

I just got to thinking that I since I’m going to be frequenting lots of wifi with my lappie, how easy is setting up a openvpn client with Mate?
Any suggestions?

2

You can do it via the network-manager . Also websites should have instructions of some sort . I sucsesfully connected to a vpn network but I have no internet while vpn is active . Maybe bouce I use a free one . It wasn’t a big deal configuring .

3

I’m guessing at the package name but…

sudo apt-get install network-manager-openvpn

should do it.

4

I actually just write a little bash script that runs ovpn from terminal. Then I add a launcher to the right of system (where ff is by default) and am good from there

1 Like
5

Now my next question should probably be do I set up a vpn server here at home and use that or should I utilize a free service or even pay for one.

@Wimpy That was a great guess!

6

I’m having trouble configuring the vpn. When I left click on network manager>configure vpn it just brings up the regular network configuration window that has no mention of adding a vpn in it. Could this be something that just isnt ready for the official 15.04 yet? I’ve reinstalled and even tried rebooting. Doing it through command line fails as well.
In command line I get…
Tue Mar 17 13:36:39 2015 ERROR: Cannot ioctl TUNSETIFF tun0: Operation not permitted (errno=1)
Tue Mar 17 13:36:39 2015 Exiting due to fatal error

Firewall blocking this maybe? I have gufw off currently.

7

Try running it as sudo

8

Sudo didnt work either.

9

These might be of use to you:

https://help.ubuntu.com/community/VPNClient

https://help.ubuntu.com/community/OpenVPN

10

Thank you @wolfman but I already been through those. I should have some time to play around this weekend. I’m thinking it’s the firewall and ports.

11

See this thread and its only answer:

Hope it helps. :smiley:

12

I’m adding my issue to this discussion.

I have gotten openvpn to work for me via terminal - but I would like to get it working through my gui network applet.

When I ‘activate’ my vpn via my network gui, it says it activates, but I have no internet access. UFW is NOT on. When I activate it via terminal - all works fine.

Any ideas to get this working via my GUI?

13

Hmm… I don’t use a firewall, but I do use OpenVPN (activated through the Network Manager Applet GUI) to connect to a paid VPN service at privateinternetaccess.com.

I never have any issues getting it working with them on any distro. I install network-manager-openvpn network-manager-openvpn-gnome and openvpn itself (might have just installed network-manager-openvpn and it pulled in the rest, can’t remember), then I manually configure the VPN per my provider’s instructions. Easy peasy.

I realize that doesn’t necessarily help you, but OpenVPN works perfectly with at least some providers on 15.04.

14

I’m using mullvad.net.

It works fine from the command line. I just had to change the ca, cert, key, and crl-verify to point to the right files on my drive.

if I run openvpn --config and point to my mullvad.conf file - vpn works perfectly.

I added the vpn stuff to the network applet as best I could. When I connect with it, it says its working, but my internet goes away. I verified I don’t have a firewall active, so that’s not it.

I’m betting there is some setting I’m missing, I just don’t know what it is.

Is there a command I can run via terminal to run what the network applet runs, to see if its generating some error I’m not seeing, maybe help diagnose the issue!

15

Hmm.. I'm over my head here, but I'll take a swing at it.

The syslog might have some info that helps us. I'll append the appropriate section of mine for comparison, at the bottom of this post.

Bring up a terminal and do this:
tail -n0 -f /var/log/syslog > /tmp/syslog

Then activate your VPN via the applet. Once it shows the active VPN icon (or errors out) immediately hit CTRL-C, which should kill the syslog being written out to that file. Then use Pluma to open and copy paste the contents of the /tmp/syslog file you created. We'll see if it gives any indication of what is wrong.

Apr 3 23:00:56 tinymite NetworkManager[627]: Starting VPN service 'openvpn'... Apr 3 23:00:56 tinymite NetworkManager[627]: VPN service 'openvpn' started (org.freedesktop.NetworkManager.openvpn), PID 10407 Apr 3 23:00:56 tinymite NetworkManager[627]: VPN service 'openvpn' appeared; activating connections Apr 3 23:00:56 tinymite NetworkManager[627]: VPN plugin state changed: starting (3) Apr 3 23:00:56 tinymite NetworkManager[627]: nm-openvpn-Message: openvpn started with pid 10412 Apr 3 23:00:56 tinymite NetworkManager[627]: VPN connection 'US East' (ConnectInteractive) reply received. Apr 3 23:00:56 tinymite nm-openvpn[10412]: OpenVPN 2.3.2 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [eurephia] [MH] [IPv6] built on Dec 1 2014 Apr 3 23:00:56 tinymite nm-openvpn[10412]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Apr 3 23:00:56 tinymite nm-openvpn[10412]: UDPv4 link local: [undef] Apr 3 23:00:56 tinymite nm-openvpn[10412]: UDPv4 link remote: [AF_INET]208.167.254.239:1194 Apr 3 23:00:57 tinymite nm-openvpn[10412]: [Private Internet Access] Peer Connection Initiated with [AF_INET]208.167.254.239:1194 Apr 3 23:00:59 tinymite NetworkManager[627]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Apr 3 23:00:59 tinymite NetworkManager[627]: (tun0): carrier is OFF Apr 3 23:00:59 tinymite NetworkManager[627]: (tun0): new Tun device (driver: 'unknown' ifindex: 6) Apr 3 23:00:59 tinymite NetworkManager[627]: (tun0): exported as /org/freedesktop/NetworkManager/Devices/5 Apr 3 23:00:59 tinymite nm-openvpn[10412]: TUN/TAP device tun0 opened Apr 3 23:00:59 tinymite nm-openvpn[10412]: /usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper --tun -- tun0 1500 1542 10.198.1.10 10.198.1.9 init Apr 3 23:00:59 tinymite NetworkManager[627]: devices added (path: /sys/devices/virtual/net/tun0, iface: tun0) Apr 3 23:00:59 tinymite NetworkManager[627]: device added (path: /sys/devices/virtual/net/tun0, iface: tun0): no ifupdown configuration found. Apr 3 23:00:59 tinymite systemd[1]: Starting ifup for tun0... Apr 3 23:00:59 tinymite sh[10433]: Unknown interface tun0 Apr 3 23:00:59 tinymite NetworkManager[627]: VPN connection 'US East' (IP Config Get) reply received. Apr 3 23:00:59 tinymite systemd[1]: Started ifup for tun0. Apr 3 23:00:59 tinymite NetworkManager[627]: VPN connection 'US East' (IP4 Config Get) reply received. Apr 3 23:00:59 tinymite NetworkManager[627]: VPN Gateway: 208.167.254.239 Apr 3 23:00:59 tinymite NetworkManager[627]: Tunnel Device: tun0 Apr 3 23:00:59 tinymite NetworkManager[627]: IPv4 configuration: Apr 3 23:00:59 tinymite NetworkManager[627]: Internal Gateway: 10.198.1.9 Apr 3 23:00:59 tinymite NetworkManager[627]: Internal Address: 10.198.1.10 Apr 3 23:00:59 tinymite NetworkManager[627]: Internal Prefix: 32 Apr 3 23:00:59 tinymite NetworkManager[627]: Internal Point-to-Point Address: 10.198.1.9 Apr 3 23:00:59 tinymite NetworkManager[627]: Maximum Segment Size (MSS): 0 Apr 3 23:00:59 tinymite NetworkManager[627]: Static Route: 10.198.1.1/32 Next Hop: 10.198.1.9 Apr 3 23:00:59 tinymite NetworkManager[627]: Forbid Default Route: no Apr 3 23:00:59 tinymite NetworkManager[627]: DNS Domain: '(none)' Apr 3 23:00:59 tinymite NetworkManager[627]: No IPv6 configuration Apr 3 23:00:59 tinymite NetworkManager[627]: (tun0): link connected Apr 3 23:00:59 tinymite nm-openvpn[10412]: Initialization Sequence Completed Apr 3 23:00:59 tinymite NetworkManager[627]: VPN connection 'US East' (IP Config Get) complete. Apr 3 23:00:59 tinymite NetworkManager[627]: VPN plugin state changed: started (4) Apr 3 23:00:59 tinymite NetworkManager[627]: NetworkManager state is now CONNECTED_LOCAL Apr 3 23:00:59 tinymite NetworkManager[627]: NetworkManager state is now CONNECTED_GLOBAL Apr 3 23:00:59 tinymite dbus[697]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Apr 3 23:00:59 tinymite NetworkManager[627]: (tun0): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41] Apr 3 23:00:59 tinymite NetworkManager[627]: (tun0): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41] Apr 3 23:00:59 tinymite NetworkManager[627]: Activation (tun0) starting connection 'tun0' Apr 3 23:00:59 tinymite NetworkManager[627]: Activation (tun0) Stage 1 of 5 (Device Prepare) scheduled... Apr 3 23:00:59 tinymite NetworkManager[627]: Activation (tun0) Stage 1 of 5 (Device Prepare) started... Apr 3 23:00:59 tinymite NetworkManager[627]: (tun0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Apr 3 23:00:59 tinymite NetworkManager[627]: Activation (tun0) Stage 2 of 5 (Device Configure) scheduled... Apr 3 23:00:59 tinymite NetworkManager[627]: Activation (tun0) Stage 1 of 5 (Device Prepare) complete. Apr 3 23:00:59 tinymite systemd[1]: Starting Network Manager Script Dispatcher Service... Apr 3 23:00:59 tinymite dbus[697]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Apr 3 23:00:59 tinymite nm-dispatcher: Dispatching action 'vpn-up' for tun0 Apr 3 23:00:59 tinymite systemd[1]: Started Network Manager Script Dispatcher Service. Apr 3 23:00:59 tinymite NetworkManager[627]: Activation (tun0) Stage 2 of 5 (Device Configure) starting... Apr 3 23:00:59 tinymite NetworkManager[627]: (tun0): device state change: prepare -> config (reason 'none') [40 50 0] Apr 3 23:00:59 tinymite NetworkManager[627]: Activation (tun0) Stage 2 of 5 (Device Configure) successful. Apr 3 23:00:59 tinymite NetworkManager[627]: Activation (tun0) Stage 3 of 5 (IP Configure Start) scheduled. Apr 3 23:00:59 tinymite NetworkManager[627]: Activation (tun0) Stage 2 of 5 (Device Configure) complete. Apr 3 23:00:59 tinymite NetworkManager[627]: Activation (tun0) Stage 3 of 5 (IP Configure Start) started... Apr 3 23:00:59 tinymite NetworkManager[627]: (tun0): device state change: config -> ip-config (reason 'none') [50 70 0] Apr 3 23:00:59 tinymite NetworkManager[627]: Activation (tun0) Stage 5 of 5 (IPv4 Configure Commit) scheduled... Apr 3 23:00:59 tinymite NetworkManager[627]: Activation (tun0) Stage 3 of 5 (IP Configure Start) complete. Apr 3 23:00:59 tinymite NetworkManager[627]: Activation (tun0) Stage 5 of 5 (IPv4 Commit) started... Apr 3 23:00:59 tinymite NetworkManager[627]: Could not send ARP for local address 10.198.1.10: Failed to execute child process "/usr/bin/arping" (No such file or directory) Apr 3 23:00:59 tinymite NetworkManager[627]: (tun0): device state change: ip-config -> ip-check (reason 'none') [70 80 0] Apr 3 23:00:59 tinymite NetworkManager[627]: Activation (tun0) Stage 5 of 5 (IPv4 Commit) complete. Apr 3 23:00:59 tinymite NetworkManager[627]: (tun0): device state change: ip-check -> secondaries (reason 'none') [80 90 0] Apr 3 23:00:59 tinymite NetworkManager[627]: (tun0): device state change: secondaries -> activated (reason 'none') [90 100 0] Apr 3 23:00:59 tinymite NetworkManager[627]: Activation (tun0) successful, device activated. Apr 3 23:00:59 tinymite whoopsie[678]: [23:00:59] offline Apr 3 23:00:59 tinymite whoopsie[678]: [23:00:59] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/5 Apr 3 23:00:59 tinymite whoopsie[678]: [23:00:59] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/5 Apr 3 23:00:59 tinymite whoopsie[678]: [23:00:59] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/5 Apr 3 23:00:59 tinymite whoopsie[678]: [23:00:59] online Apr 3 23:00:59 tinymite nm-dispatcher: Dispatching action 'up' for tun0 Apr 3 23:00:59 tinymite systemd[1]: Stopping LSB: Start NTP daemon... Apr 3 23:00:59 tinymite ntp[10537]: * Stopping NTP server ntpd Apr 3 23:00:59 tinymite ntpd[10379]: ntpd exiting on signal 15 Apr 3 23:00:59 tinymite ntp[10537]: ...done. Apr 3 23:00:59 tinymite systemd[1]: Stopped LSB: Start NTP daemon. Apr 3 23:01:02 tinymite NetworkManager[627]: Could not send ARP for local address 10.198.1.10: Failed to execute child process "/usr/bin/arping" (No such file or directory)
16

Ok - Here’s what I got - nothing stands out to me as to why it wouldn’t work…

Apr 4 00:33:13 DOCTOR NetworkManager[713]: Starting VPN service 'openvpn'... Apr 4 00:33:13 DOCTOR NetworkManager[713]: VPN service 'openvpn' started (org.freedesktop.NetworkManager.openvpn), PID 14942 Apr 4 00:33:13 DOCTOR NetworkManager[713]: VPN service 'openvpn' appeared; activating connections Apr 4 00:33:13 DOCTOR NetworkManager[713]: VPN plugin state changed: init (1) Apr 4 00:33:13 DOCTOR NetworkManager[713]: VPN plugin state changed: starting (3) Apr 4 00:33:13 DOCTOR nm-openvpn[14945]: OpenVPN 2.3.2 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [eurephia] [MH] [IPv6] built on Dec 1 2014 Apr 4 00:33:13 DOCTOR nm-openvpn[14945]: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info. Apr 4 00:33:13 DOCTOR nm-openvpn[14945]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Apr 4 00:33:13 DOCTOR nm-openvpn[14945]: WARNING: file '/home/chris/Work/mullvad/mullvad.key' is group or others accessible Apr 4 00:33:13 DOCTOR NetworkManager[713]: VPN connection 'MullVAD' (ConnectInteractive) reply received. Apr 4 00:33:13 DOCTOR NetworkManager[713]: nm-openvpn-Message: openvpn started with pid 14945 Apr 4 00:33:13 DOCTOR nm-openvpn[14945]: UDPv4 link local: [undef] Apr 4 00:33:13 DOCTOR nm-openvpn[14945]: UDPv4 link remote: [AF_INET]46.21.99.25:1194 Apr 4 00:33:19 DOCTOR nm-openvpn[14945]: WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1541', remote='link-mtu 1542' Apr 4 00:33:19 DOCTOR nm-openvpn[14945]: WARNING: 'comp-lzo' is present in remote config but missing in local config, remote='comp-lzo' Apr 4 00:33:19 DOCTOR nm-openvpn[14945]: [se1.mullvad.net] Peer Connection Initiated with [AF_INET]46.21.99.25:1194 Apr 4 00:33:21 DOCTOR NetworkManager[713]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Apr 4 00:33:21 DOCTOR NetworkManager[713]: (tun0): carrier is OFF Apr 4 00:33:21 DOCTOR NetworkManager[713]: (tun0): new Tun device (driver: 'unknown' ifindex: 12) Apr 4 00:33:21 DOCTOR NetworkManager[713]: (tun0): exported as /org/freedesktop/NetworkManager/Devices/11 Apr 4 00:33:21 DOCTOR nm-openvpn[14945]: TUN/TAP device tun0 opened Apr 4 00:33:21 DOCTOR nm-openvpn[14945]: /usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper --tun -- tun0 1500 1541 10.8.0.42 255.255.0.0 init Apr 4 00:33:21 DOCTOR NetworkManager[713]: devices added (path: /sys/devices/virtual/net/tun0, iface: tun0) Apr 4 00:33:21 DOCTOR NetworkManager[713]: device added (path: /sys/devices/virtual/net/tun0, iface: tun0): no ifupdown configuration found. Apr 4 00:33:21 DOCTOR systemd[1]: Starting ifup for tun0... Apr 4 00:33:21 DOCTOR NetworkManager[713]: VPN connection 'MullVAD' (IP Config Get) reply received. Apr 4 00:33:21 DOCTOR NetworkManager[713]: VPN connection 'MullVAD' (IP4 Config Get) reply received. Apr 4 00:33:21 DOCTOR nm-openvpn[14945]: Initialization Sequence Completed Apr 4 00:33:21 DOCTOR NetworkManager[713]: VPN connection 'MullVAD' (IP6 Config Get) reply received. Apr 4 00:33:21 DOCTOR NetworkManager[713]: VPN Gateway: 46.21.99.25 Apr 4 00:33:21 DOCTOR NetworkManager[713]: Tunnel Device: tun0 Apr 4 00:33:21 DOCTOR NetworkManager[713]: IPv4 configuration: Apr 4 00:33:21 DOCTOR NetworkManager[713]: Internal Gateway: 10.8.0.1 Apr 4 00:33:21 DOCTOR NetworkManager[713]: Internal Address: 10.8.0.42 Apr 4 00:33:21 DOCTOR NetworkManager[713]: Internal Prefix: 16 Apr 4 00:33:21 DOCTOR NetworkManager[713]: Internal Point-to-Point Address: 0.0.0.0 Apr 4 00:33:21 DOCTOR NetworkManager[713]: Maximum Segment Size (MSS): 0 Apr 4 00:33:21 DOCTOR NetworkManager[713]: Forbid Default Route: yes Apr 4 00:33:21 DOCTOR NetworkManager[713]: Internal DNS: 10.8.0.1 Apr 4 00:33:21 DOCTOR NetworkManager[713]: DNS Domain: '(none)' Apr 4 00:33:21 DOCTOR NetworkManager[713]: IPv6 configuration: Apr 4 00:33:21 DOCTOR NetworkManager[713]: Internal Address: fd07:698a:921f:8::1028 Apr 4 00:33:21 DOCTOR NetworkManager[713]: Internal Prefix: 112 Apr 4 00:33:21 DOCTOR NetworkManager[713]: Internal Point-to-Point Address: fd07:698a:921f:8:: Apr 4 00:33:21 DOCTOR NetworkManager[713]: Maximum Segment Size (MSS): 0 Apr 4 00:33:21 DOCTOR NetworkManager[713]: Static Route: ::/2 Next Hop: fd07:698a:921f:8:: Apr 4 00:33:21 DOCTOR NetworkManager[713]: Static Route: 4000::/2 Next Hop: fd07:698a:921f:8:: Apr 4 00:33:21 DOCTOR NetworkManager[713]: Static Route: 8000::/2 Next Hop: fd07:698a:921f:8:: Apr 4 00:33:21 DOCTOR NetworkManager[713]: Static Route: c000::/2 Next Hop: fd07:698a:921f:8:: Apr 4 00:33:21 DOCTOR NetworkManager[713]: Forbid Default Route: no Apr 4 00:33:21 DOCTOR NetworkManager[713]: DNS Domain: '(none)' Apr 4 00:33:21 DOCTOR NetworkManager[713]: VPN plugin state changed: started (4) Apr 4 00:33:21 DOCTOR systemd[1]: Started ifup for tun0. Apr 4 00:33:21 DOCTOR sh[14956]: Unknown interface tun0 Apr 4 00:33:21 DOCTOR NetworkManager[713]: Policy set 'MullVAD' (tun0) as default for IPv6 routing and DNS. Apr 4 00:33:21 DOCTOR NetworkManager[713]: Writing DNS information to /sbin/resolvconf Apr 4 00:33:21 DOCTOR dnsmasq[861]: setting upstream servers from DBus Apr 4 00:33:21 DOCTOR dnsmasq[861]: using nameserver 10.8.0.1#53 for domain 10.in-addr.arpa Apr 4 00:33:21 DOCTOR dbus[753]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Apr 4 00:33:21 DOCTOR systemd[1]: Starting Network Manager Script Dispatcher Service... Apr 4 00:33:21 DOCTOR NetworkManager[713]: (tun0): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41] Apr 4 00:33:21 DOCTOR NetworkManager[713]: (tun0): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41] Apr 4 00:33:21 DOCTOR NetworkManager[713]: Activation (tun0) starting connection 'tun0' Apr 4 00:33:21 DOCTOR NetworkManager[713]: Activation (tun0) Stage 1 of 5 (Device Prepare) scheduled... Apr 4 00:33:21 DOCTOR NetworkManager[713]: Activation (tun0) Stage 1 of 5 (Device Prepare) started... Apr 4 00:33:21 DOCTOR NetworkManager[713]: (tun0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Apr 4 00:33:21 DOCTOR NetworkManager[713]: Activation (tun0) Stage 2 of 5 (Device Configure) scheduled... Apr 4 00:33:21 DOCTOR NetworkManager[713]: Activation (tun0) Stage 1 of 5 (Device Prepare) complete. Apr 4 00:33:21 DOCTOR dbus[753]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Apr 4 00:33:21 DOCTOR systemd[1]: Started Network Manager Script Dispatcher Service. Apr 4 00:33:21 DOCTOR nm-dispatcher: Dispatching action 'vpn-up' for tun0 Apr 4 00:33:21 DOCTOR NetworkManager[713]: Activation (tun0) Stage 2 of 5 (Device Configure) starting... Apr 4 00:33:21 DOCTOR NetworkManager[713]: (tun0): device state change: prepare -> config (reason 'none') [40 50 0] Apr 4 00:33:21 DOCTOR NetworkManager[713]: Activation (tun0) Stage 2 of 5 (Device Configure) successful. Apr 4 00:33:21 DOCTOR NetworkManager[713]: Activation (tun0) Stage 3 of 5 (IP Configure Start) scheduled. Apr 4 00:33:21 DOCTOR NetworkManager[713]: Activation (tun0) Stage 2 of 5 (Device Configure) complete. Apr 4 00:33:21 DOCTOR NetworkManager[713]: Activation (tun0) Stage 3 of 5 (IP Configure Start) started... Apr 4 00:33:21 DOCTOR NetworkManager[713]: (tun0): device state change: config -> ip-config (reason 'none') [50 70 0] Apr 4 00:33:21 DOCTOR NetworkManager[713]: Activation (tun0) Stage 5 of 5 (IPv4 Configure Commit) scheduled... Apr 4 00:33:21 DOCTOR NetworkManager[713]: Activation (tun0) Stage 5 of 5 (IPv6 Commit) scheduled... Apr 4 00:33:21 DOCTOR NetworkManager[713]: Activation (tun0) Stage 3 of 5 (IP Configure Start) complete. Apr 4 00:33:21 DOCTOR NetworkManager[713]: Activation (tun0) Stage 5 of 5 (IPv4 Commit) started... Apr 4 00:33:21 DOCTOR NetworkManager[713]: Could not send ARP for local address 10.8.0.42: Failed to execute child process "/usr/bin/arping" (No such file or directory) Apr 4 00:33:21 DOCTOR NetworkManager[713]: (tun0): device state change: ip-config -> ip-check (reason 'none') [70 80 0] Apr 4 00:33:21 DOCTOR NetworkManager[713]: Activation (tun0) Stage 5 of 5 (IPv4 Commit) complete. Apr 4 00:33:21 DOCTOR NetworkManager[713]: Activation (tun0) Stage 5 of 5 (IPv6 Commit) started... Apr 4 00:33:21 DOCTOR NetworkManager[713]: Activation (tun0) Stage 5 of 5 (IPv6 Commit) complete. Apr 4 00:33:21 DOCTOR NetworkManager[713]: (tun0): device state change: ip-check -> secondaries (reason 'none') [80 90 0] Apr 4 00:33:21 DOCTOR NetworkManager[713]: (tun0): device state change: secondaries -> activated (reason 'none') [90 100 0] Apr 4 00:33:21 DOCTOR NetworkManager[713]: Activation (tun0) successful, device activated. Apr 4 00:33:21 DOCTOR systemd[1]: Stopping LSB: Start NTP daemon... Apr 4 00:33:21 DOCTOR ntp[15071]: * Stopping NTP server ntpd Apr 4 00:33:21 DOCTOR ntpd[14827]: ntpd exiting on signal 15 Apr 4 00:33:21 DOCTOR ntp[15071]: ...done. Apr 4 00:33:21 DOCTOR systemd[1]: Stopped LSB: Start NTP daemon. Apr 4 00:33:21 DOCTOR ntpdate[15086]: name server cannot be used: Temporary failure in name resolution (-3) Apr 4 00:33:21 DOCTOR nm-dispatcher: Dispatching action 'up' for tun0 Apr 4 00:33:21 DOCTOR systemd[1]: Starting LSB: Start NTP daemon... Apr 4 00:33:21 DOCTOR ntp[15144]: * Starting NTP server ntpd Apr 4 00:33:21 DOCTOR ntpd[15160]: ntpd [email protected] Mon Feb 9 18:11:57 UTC 2015 (1) Apr 4 00:33:21 DOCTOR ntpd[15167]: proto: precision = 0.120 usec Apr 4 00:33:21 DOCTOR ntpd[15167]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Apr 4 00:33:21 DOCTOR ntpd[15167]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 Apr 4 00:33:21 DOCTOR ntp[15144]: ...done. Apr 4 00:33:21 DOCTOR systemd[1]: Started LSB: Start NTP daemon. Apr 4 00:33:21 DOCTOR ntpd[15167]: Listen and drop on 1 v6wildcard :: UDP 123 Apr 4 00:33:21 DOCTOR ntpd[15167]: Listen normally on 2 lo 127.0.0.1 UDP 123 Apr 4 00:33:21 DOCTOR ntpd[15167]: Listen normally on 3 eth0 192.168.247.248 UDP 123 Apr 4 00:33:21 DOCTOR ntpd[15167]: Listen normally on 4 tun0 10.8.0.42 UDP 123 Apr 4 00:33:21 DOCTOR ntpd[15167]: Listen normally on 5 lo ::1 UDP 123 Apr 4 00:33:21 DOCTOR ntpd[15167]: Listen normally on 6 tun0 fd07:698a:921f:8::1028 UDP 123 Apr 4 00:33:21 DOCTOR ntpd[15167]: Listen normally on 7 eth0 fe80::ea94:f6ff:fe00:c417 UDP 123 Apr 4 00:33:21 DOCTOR ntpd[15167]: peers refreshed Apr 4 00:33:21 DOCTOR ntpd[15167]: Listening on routing socket on fd #24 for interface updates Apr 4 00:33:21 DOCTOR ntpd[15167]: Deferring DNS for 0.ubuntu.pool.ntp.org 1 Apr 4 00:33:21 DOCTOR ntpd[15167]: Deferring DNS for 1.ubuntu.pool.ntp.org 1 Apr 4 00:33:21 DOCTOR ntpd[15167]: Deferring DNS for 2.ubuntu.pool.ntp.org 1 Apr 4 00:33:21 DOCTOR ntpd[15167]: Deferring DNS for 3.ubuntu.pool.ntp.org 1 Apr 4 00:33:21 DOCTOR ntpd[15167]: Deferring DNS for ntp.ubuntu.com 1 Apr 4 00:33:21 DOCTOR ntpd[15172]: signal_no_reset: signal 17 had flags 4000000 Apr 4 00:33:21 DOCTOR systemd[1]: Stopping LSB: Start NTP daemon... Apr 4 00:33:21 DOCTOR ntp[15243]: * Stopping NTP server ntpd Apr 4 00:33:21 DOCTOR ntpd[15167]: ntpd exiting on signal 15 Apr 4 00:33:21 DOCTOR ntp[15243]: ...done. Apr 4 00:33:21 DOCTOR systemd[1]: Stopped LSB: Start NTP daemon. Apr 4 00:33:21 DOCTOR ntpdate[15260]: name server cannot be used: Temporary failure in name resolution (-3) Apr 4 00:33:21 DOCTOR systemd[1]: Starting LSB: Start NTP daemon... Apr 4 00:33:21 DOCTOR ntp[15309]: * Starting NTP server ntpd Apr 4 00:33:21 DOCTOR ntpd[15317]: ntpd [email protected] Mon Feb 9 18:11:57 UTC 2015 (1) Apr 4 00:33:21 DOCTOR ntpd[15318]: proto: precision = 0.102 usec Apr 4 00:33:21 DOCTOR ntpd[15318]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Apr 4 00:33:21 DOCTOR ntpd[15318]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 Apr 4 00:33:21 DOCTOR ntp[15309]: ...done. Apr 4 00:33:21 DOCTOR systemd[1]: Started LSB: Start NTP daemon. Apr 4 00:33:21 DOCTOR ntpd[15318]: Listen and drop on 1 v6wildcard :: UDP 123 Apr 4 00:33:21 DOCTOR ntpd[15318]: Listen normally on 2 lo 127.0.0.1 UDP 123 Apr 4 00:33:21 DOCTOR ntpd[15318]: Listen normally on 3 eth0 192.168.247.248 UDP 123 Apr 4 00:33:21 DOCTOR ntpd[15318]: Listen normally on 4 tun0 10.8.0.42 UDP 123 Apr 4 00:33:21 DOCTOR ntpd[15318]: Listen normally on 5 lo ::1 UDP 123 Apr 4 00:33:21 DOCTOR ntpd[15318]: Listen normally on 6 tun0 fd07:698a:921f:8::1028 UDP 123 Apr 4 00:33:21 DOCTOR ntpd[15318]: Listen normally on 7 eth0 fe80::ea94:f6ff:fe00:c417 UDP 123 Apr 4 00:33:21 DOCTOR ntpd[15318]: peers refreshed Apr 4 00:33:21 DOCTOR ntpd[15318]: Listening on routing socket on fd #24 for interface updates Apr 4 00:33:21 DOCTOR ntpd[15318]: Deferring DNS for 0.ubuntu.pool.ntp.org 1 Apr 4 00:33:21 DOCTOR ntpd[15318]: Deferring DNS for 1.ubuntu.pool.ntp.org 1 Apr 4 00:33:21 DOCTOR ntpd[15318]: Deferring DNS for 2.ubuntu.pool.ntp.org 1 Apr 4 00:33:21 DOCTOR ntpd[15318]: Deferring DNS for 3.ubuntu.pool.ntp.org 1 Apr 4 00:33:21 DOCTOR ntpd[15318]: Deferring DNS for ntp.ubuntu.com 1 Apr 4 00:33:21 DOCTOR ntpd[15321]: signal_no_reset: signal 17 had flags 4000000 Apr 4 00:33:23 DOCTOR NetworkManager[713]: Could not send ARP for local address 10.8.0.42: Failed to execute child process "/usr/bin/arping" (No such file or directory) Apr 4 00:33:23 DOCTOR ntpd_intres[15172]: parent died before we finished, exiting Apr 4 00:33:26 DOCTOR systemd[1]: Stopping LSB: Start NTP daemon... Apr 4 00:33:26 DOCTOR ntp[15348]: * Stopping NTP server ntpd Apr 4 00:33:26 DOCTOR ntpd[15318]: ntpd exiting on signal 15 Apr 4 00:33:26 DOCTOR ntp[15348]: ...done. Apr 4 00:33:26 DOCTOR systemd[1]: Stopped LSB: Start NTP daemon. Apr 4 00:33:26 DOCTOR ntpdate[15357]: name server cannot be used: Temporary failure in name resolution (-3) Apr 4 00:33:26 DOCTOR systemd[1]: Starting LSB: Start NTP daemon... Apr 4 00:33:26 DOCTOR ntp[15382]: * Starting NTP server ntpd Apr 4 00:33:26 DOCTOR ntpd[15390]: ntpd [email protected] Mon Feb 9 18:11:57 UTC 2015 (1) Apr 4 00:33:26 DOCTOR ntp[15382]: ...done. Apr 4 00:33:26 DOCTOR ntpd[15391]: proto: precision = 0.102 usec Apr 4 00:33:26 DOCTOR ntpd[15391]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Apr 4 00:33:26 DOCTOR ntpd[15391]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 Apr 4 00:33:26 DOCTOR systemd[1]: Started LSB: Start NTP daemon. Apr 4 00:33:26 DOCTOR ntpd[15391]: Listen and drop on 1 v6wildcard :: UDP 123 Apr 4 00:33:26 DOCTOR ntpd[15391]: Listen normally on 2 lo 127.0.0.1 UDP 123 Apr 4 00:33:26 DOCTOR ntpd[15391]: Listen normally on 3 eth0 192.168.247.248 UDP 123 Apr 4 00:33:26 DOCTOR ntpd[15391]: Listen normally on 4 tun0 10.8.0.42 UDP 123 Apr 4 00:33:26 DOCTOR ntpd[15391]: Listen normally on 5 lo ::1 UDP 123 Apr 4 00:33:26 DOCTOR ntpd[15391]: Listen normally on 6 tun0 fd07:698a:921f:8::1028 UDP 123 Apr 4 00:33:26 DOCTOR ntpd[15391]: Listen normally on 7 eth0 fe80::ea94:f6ff:fe00:c417 UDP 123 Apr 4 00:33:26 DOCTOR ntpd[15391]: peers refreshed Apr 4 00:33:26 DOCTOR ntpd[15391]: Listening on routing socket on fd #24 for interface updates Apr 4 00:33:26 DOCTOR ntpd[15391]: Deferring DNS for 0.ubuntu.pool.ntp.org 1 Apr 4 00:33:26 DOCTOR ntpd[15391]: Deferring DNS for 1.ubuntu.pool.ntp.org 1 Apr 4 00:33:26 DOCTOR ntpd[15391]: Deferring DNS for 2.ubuntu.pool.ntp.org 1 Apr 4 00:33:26 DOCTOR ntpd[15391]: Deferring DNS for 3.ubuntu.pool.ntp.org 1 Apr 4 00:33:26 DOCTOR ntpd[15391]: Deferring DNS for ntp.ubuntu.com 1 Apr 4 00:33:26 DOCTOR ntpd[15393]: signal_no_reset: signal 17 had flags 4000000 Apr 4 00:33:26 DOCTOR systemd[1]: Stopping LSB: Start NTP daemon... Apr 4 00:33:26 DOCTOR ntp[15415]: * Stopping NTP server ntpd Apr 4 00:33:26 DOCTOR ntpd[15391]: ntpd exiting on signal 15 Apr 4 00:33:26 DOCTOR ntp[15415]: ...done. Apr 4 00:33:26 DOCTOR systemd[1]: Stopped LSB: Start NTP daemon. Apr 4 00:33:26 DOCTOR ntpdate[15424]: name server cannot be used: Temporary failure in name resolution (-3) Apr 4 00:33:26 DOCTOR systemd[1]: Starting LSB: Start NTP daemon... Apr 4 00:33:26 DOCTOR ntp[15449]: * Starting NTP server ntpd Apr 4 00:33:26 DOCTOR ntpd[15457]: ntpd [email protected] Mon Feb 9 18:11:57 UTC 2015 (1) Apr 4 00:33:26 DOCTOR ntpd[15458]: proto: precision = 0.109 usec Apr 4 00:33:26 DOCTOR ntpd[15458]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Apr 4 00:33:26 DOCTOR ntpd[15458]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 Apr 4 00:33:26 DOCTOR ntp[15449]: ...done. Apr 4 00:33:26 DOCTOR systemd[1]: Started LSB: Start NTP daemon. Apr 4 00:33:26 DOCTOR ntpd[15458]: Listen and drop on 1 v6wildcard :: UDP 123 Apr 4 00:33:26 DOCTOR ntpd[15458]: Listen normally on 2 lo 127.0.0.1 UDP 123 Apr 4 00:33:26 DOCTOR ntpd[15458]: Listen normally on 3 eth0 192.168.247.248 UDP 123 Apr 4 00:33:26 DOCTOR ntpd[15458]: Listen normally on 4 tun0 10.8.0.42 UDP 123 Apr 4 00:33:26 DOCTOR ntpd[15458]: Listen normally on 5 lo ::1 UDP 123 Apr 4 00:33:26 DOCTOR ntpd[15458]: Listen normally on 6 tun0 fd07:698a:921f:8::1028 UDP 123 Apr 4 00:33:26 DOCTOR ntpd[15458]: Listen normally on 7 eth0 fe80::ea94:f6ff:fe00:c417 UDP 123 Apr 4 00:33:26 DOCTOR ntpd[15458]: peers refreshed Apr 4 00:33:26 DOCTOR ntpd[15458]: Listening on routing socket on fd #24 for interface updates Apr 4 00:33:26 DOCTOR ntpd[15458]: Deferring DNS for 0.ubuntu.pool.ntp.org 1 Apr 4 00:33:26 DOCTOR ntpd[15458]: Deferring DNS for 1.ubuntu.pool.ntp.org 1 Apr 4 00:33:26 DOCTOR ntpd[15458]: Deferring DNS for 2.ubuntu.pool.ntp.org 1 Apr 4 00:33:26 DOCTOR ntpd[15458]: Deferring DNS for 3.ubuntu.pool.ntp.org 1 Apr 4 00:33:26 DOCTOR ntpd[15458]: Deferring DNS for ntp.ubuntu.com 1 Apr 4 00:33:26 DOCTOR ntpd[15461]: signal_no_reset: signal 17 had flags 4000000 Apr 4 00:33:28 DOCTOR ntpd_intres[15393]: parent died before we finished, exiting Apr 4 00:33:30 DOCTOR nm-openvpn[14945]: write to TUN/TAP : Invalid argument (code=22)

But I’ve got no idea from looking at that!

17

Hmm... Two things that stand out to me:

Apr 4 00:33:19 DOCTOR nm-openvpn14945: WARNING: 'comp-lzo' is present in remote config but missing in local config, remote='comp-lzo'

  1. It doesn't look like you have LZO compression enabled, and it looks like your provider requires it.

Apr 4 00:33:19 DOCTOR nm-openvpn14945: WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1541', remote='link-mtu 1542'

and I'm not sure about the MTU issue... typo? Fix the compression issue first and see if that does the trick. If not, delete anything MTU related or at least make it match the server's config.

Cross your fingers and try it again :smiley:

For reference... different provider though, so don't worry about the other stuff.

Screenshot-OpenVPN Advanced Options.png573×514 55.1 KB

18

I’m blathering (it’s way past my bedtime) but I bet it’s just the compression issue. It looks like the link may be going active for you, but it can’t talk (or resolve IP addresses).

I’ll try and help you dig deeper tomorrow, if correcting that doesn’t do the trick.

Night! :smile:

19

Okay -

Checked the LZO data compression and tried - no change.
Checked the Use Custom Tunnel MTU and set to 1542 - no change as well.

Also, for the record, when I checked Use TCP Connection - it wouldn’t even load ( timed out ).

The other problem is the instructions from Mullvad say to Import their conf file - but I don’t see how you import into Network Manager in 15.04!

And thanks for the help so far!!!

20

Oh, the import feature is a little wonky.

In the NM Applet “left click and go to” VPN Connections / Configure VPN / Add / Import a Saved VPN Configuration / Create / and then select your config file.

Delete your existing connection first, just so there’s no confusion.

Edit: My provider’s config files end in .ovpn but that might just be a naming convenience for them.