openvpn requires a restart

mh-active · 2018-03-18 17:38:59

Hi There,

I come across a strange issue. Until a couple of days ago my openvpn client was working fine on my arch server.
However today I relazied that something was wrong, the openvpn connection was not running.
So I started some analyis and realizied that after 2nd systemctl restart everything was fine.
I tried several things, but whatever I did I had to start the service twice. No matter if I did this via systemctl or directly start openvpn --config.

At first I thought it's because of the new openvpn package, so I downgraded but still same issue.

Thus my querstion, did somebody see the same issue?

Cheers,
Marco

graysky · 2018-03-18 17:57:09

I am finding this to be the case too on a Raspberry Pi system running Arch ARM; My Arch box (x86_64) which runs it seems unaffected. On what distro and package version are you noticing this?

mh-active · 2018-03-18 18:21:54

regular arch installation with openvpn-2.4.5-1-x86_64 (latest). It's a virtual machine on KVM

graysky · 2018-03-18 18:32:04

I am using it as a client in a linux container and am not experiencing this issue (x86_64). I have an ARM device running Arch ARM aarch64 running openvpn as a server and I am not experiencing this issue. I only see it on an Arch ARM (armv7h) box running openvpn as a client.

R00KIE · 2018-03-18 18:41:19

I would suggest that you try to connect manually and inspect the output of openvpn. If the output does not have anything that looks "interesting" increase the verbosity of the output. If anything the point where it stops/hangs is a clue already, also look in the server logs (if you control the server) as there may be hints at why things are not working.

That said, and without wanting to turn this into an arm thread, I do have an arm board (cubieboard2 - armv7h) with arch arm and with openvpn both as server and client and I haven't noticed any problems.

mh-active · 2018-03-18 20:24:54

I did and they are the same, also the server is not ginving any interesting details. The only difference that that I can see is after running "ip a":

After the 1st start it's like:

3: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 100
    link/none
    inet6 fe80::44f9:5aca:d3a5:f6e3/64 scope link stable-privacy
       valid_lft forever preferred_lft forever

and after the 2nd start it's:

4: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 100
    link/none
    inet 172.23.1.13/23 brd 172.23.1.255 scope global tun0
       valid_lft forever preferred_lft forever
    inet6 fe80::6995:55e9:c7d2:6fe3/64 scope link stable-privacy
       valid_lft forever preferred_lft forever

graysky · 2018-03-18 21:49:50

I have noticed the same (although I haven't yet tried starting it manually) and again, my observations are on Arch ARM.

Arch Linux

#1 2018-03-18 17:38:59

openvpn requires a restart

#2 2018-03-18 17:57:09

Re: openvpn requires a restart

#3 2018-03-18 18:21:54

Re: openvpn requires a restart

#4 2018-03-18 18:32:04

Re: openvpn requires a restart

#5 2018-03-18 18:41:19

Re: openvpn requires a restart

#6 2018-03-18 20:24:54

Re: openvpn requires a restart

#7 2018-03-18 21:49:50

Re: openvpn requires a restart

Board footer