Issues with server Internet dying randomly (dietpi) (OpenVPN)

froodle · November 22, 2019

Having an issue were my dietPi's internet is dying randomly after 1+ hours of being online, seems to be randomly timed

Raspberry Pi running DietPi connected by wifi
Running OpenVPN on startup
cant see any logging related to it even after chaning dietPi's logging to store it all.
It seems i can still get local access to it on the network but no internet on it
I wonder if its issue with the OpenVPN

ip link show shows

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode D EFAULT group default qlen 1000
link/ether dc:a6:32:32:22:f5 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP m ode DORMANT group default qlen 1000
link/ether dc:a6:32:32:22:f6 brd ff:ff:ff:ff:ff:ff
4: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast sta te UNKNOWN mode DEFAULT group default qlen 100
link/none

/etc/network/interfaces has

# Drop-in configs
source interfaces.d/*

# Local
auto lo
iface lo inet loopback

# Ethernet
allow-hotplug eth0
iface eth0 inet dhcp
address 0.0.0.0
netmask 0.0.0.0
gateway 0.0.0.0
#dns-nameservers 0.0.0.0

# WiFi
allow-hotplug wlan0
iface wlan0 inet static
address 192.168.1.217
netmask 255.255.255.0
gateway 192.168.1.1
dns-nameservers 8.8.8.8
wireless-power off
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

Any ideas?

Thanks

froodle · November 23, 2019

I stopped the VPN service and see my internet reconnect so enabled verbose logging on my openvpn and got

Fri Nov 22 22:07:42 2019 Authenticate/Decrypt packet error: bad packet ID (may b e a replay): [ #793246 ] -- see the man page entry for --no-replay and --replay- window for more info or silence this warning with --mute-replay-warnings
Fri Nov 22 22:19:58 2019 [f614301ffb289b9e6b8e82726c4cc1fd] Inactivity timeout ( --ping-restart), restarting
Fri Nov 22 22:19:58 2019 SIGUSR1[soft,ping-restart] received, process restarting
Fri Nov 22 22:20:03 2019 TCP/UDP: Preserving recently used remote address: [AF_I NET]89.238.150.4:1198
Fri Nov 22 22:20:03 2019 UDP link local: (not bound)
Fri Nov 22 22:20:03 2019 UDP link remote: [AF_INET]89.238.150.4:1198
Fri Nov 22 22:21:03 2019 TLS Error: TLS key negotiation failed to occur within 6 0 seconds (check your network connectivity)
Fri Nov 22 22:21:03 2019 TLS Error: TLS handshake failed

at this point my internet cant be used on the device (lan works fine though)
and 10 minutes later i get the following logs

Fri Nov 22 22:34:48 2019 RESOLVE: Cannot resolve host address: uk-london.private internetaccess.com:1198 (Temporary failure in name resolution)
Fri Nov 22 22:34:48 2019 Could not determine IPv4/IPv6 protocol
Fri Nov 22 22:34:48 2019 SIGUSR1[soft,init_instance] received, process restartin g
Fri Nov 22 22:35:13 2019 RESOLVE: Cannot resolve host address: uk-london.private internetaccess.com:1198 (Temporary failure in name resolution)
Fri Nov 22 22:35:33 2019 RESOLVE: Cannot resolve host address: uk-london.private internetaccess.com:1198 (Temporary failure in name resolution)
Fri Nov 22 22:35:33 2019 Could not determine IPv4/IPv6 protocol

Any help?