tun0 connection breaks

dualsbiker

Hello,

I have a problem and I don't know how to start solving it. I have a small PC, a BananaPi, and LTE modem. The Pi is connected via OpenVPN connection as a client to a server. When I start the client it connects to the server and when I check ifconfig I can see the tun0 interface. After some time, e.g. 1h, I loose the connection and the tun0 interface disappears. But it doesn't loose connection to the internet.
What do I have to do, that you can help me?

thanks

TinCanTech

Please contact your server administrator.

dualsbiker

So I got the following log file from server administrator. He said, that there's an inactivity timeout and the server tries to reconnect to the client. The IP of the client has changed and OpenVPN starts a new session. I don't know why the IP of the client has changed, it's standing in my desk and isn't moving.

Mon Oct 28 08:46:48 2019 us=892860 109.41.15.26:34593 VERIFY OK: depth=0, C=DE, ST=YYY, O=XXX, OU=TS-BAN, CN=HPAHH;6007
Mon Oct 28 08:46:49 2019 us=170888 109.41.15.26:34593 [HPAHH;6007] Peer Connection Initiated with [AF_INET]109.41.15.26:34593
Mon Oct 28 08:46:49 2019 us=170940 HPAHH;6007/109.41.15.26:34593 MULTI_sva: pool returned IPv4=192.168.77.42, IPv6=(Not enabled)
Mon Oct 28 08:46:49 2019 us=171067 HPAHH;6007/109.41.15.26:34593 MULTI: Learn: 192.168.77.42 -> HPAHH;6007/109.41.15.26:34593
Mon Oct 28 08:46:49 2019 us=171103 HPAHH;6007/109.41.15.26:34593 MULTI: primary virtual IP for HPAHH;6007/109.41.15.26:34593: 192.168.77.42
Mon Oct 28 08:46:51 2019 us=330928 HPAHH;6007/109.41.15.26:34593 PUSH: Received control message: 'PUSH_REQUEST'
Mon Oct 28 08:46:51 2019 us=331080 HPAHH;6007/109.41.15.26:34593 SENT CONTROL [HPAHH;6007]: 'PUSH_REPLY,route-gateway 192.168.77.1,topology subnet,ping 60,ping-restart 360,ifconfig 192.168.77.42 255.255.255.0,peer-id 2' (status=1)
Mon Oct 28 08:47:00 2019 us=770812 109.41.15.26:53256 VERIFY OK: depth=0, C=DE, ST=YYY, O=XXX, OU=TS-BAN, CN=HPAHH;6007
Mon Oct 28 08:47:04 2019 us=69715 109.41.15.26:53256 [HPAHH;6007] Peer Connection Initiated with [AF_INET]109.41.15.26:53256
Mon Oct 28 08:47:04 2019 us=69852 MULTI: new connection by client 'HPAHH;6007' will cause previous active sessions by this client to be dropped.  Remember to use the --duplicate-cn option if you want multiple clients using the same certificate or username to concurrently connect.
Mon Oct 28 08:47:04 2019 us=69906 MULTI: Learn: 192.168.77.42 -> HPAHH;6007/109.41.15.26:53256
Mon Oct 28 08:47:04 2019 us=69914 MULTI: primary virtual IP for HPAHH;6007/109.41.15.26:53256: 192.168.77.42
Mon Oct 28 08:47:06 2019 us=449438 HPAHH;6007/109.41.15.26:53256 PUSH: Received control message: 'PUSH_REQUEST'
Mon Oct 28 08:47:06 2019 us=449544 HPAHH;6007/109.41.15.26:53256 SENT CONTROL [HPAHH;6007]: 'PUSH_REPLY,route-gateway 192.168.77.1,topology subnet,ping 60,ping-restart 360,ifconfig 192.168.77.42 255.255.255.0,peer-id 3' (status=1)
Mon Oct 28 08:59:08 2019 us=367292 HPAHH;6007/109.41.15.26:53256 [HPAHH;6007] Inactivity timeout (--ping-restart), restarting
Mon Oct 28 08:59:08 2019 us=367357 HPAHH;6007/109.41.15.26:53256 SIGUSR1[soft,ping-restart] received, client-instance restarting
Mon Oct 28 09:35:34 2019 us=700602 109.41.8.81:56851 VERIFY OK: depth=0, C=DE, ST=YYY, O=XXX, OU=TS-BAN, CN=HPAHH;6007
Mon Oct 28 09:35:37 2019 us=171674 109.41.8.81:38729 VERIFY OK: depth=0, C=DE, ST=YYY, O=XXX, OU=TS-BAN, CN=HPAHH;6007
Mon Oct 28 09:35:37 2019 us=309624 109.41.8.81:38729 [HPAHH;6007] Peer Connection Initiated with [AF_INET]109.41.8.81:38729
Mon Oct 28 09:35:37 2019 us=309821 MULTI: new connection by client 'HPAHH;6007' will cause previous active sessions by this client to be dropped.  Remember to use the --duplicate-cn option if you want multiple clients using the same certificate or username to concurrently connect.
Mon Oct 28 09:35:37 2019 us=309918 MULTI: Learn: 192.168.77.42 -> HPAHH;6007/109.41.8.81:38729
Mon Oct 28 09:35:37 2019 us=309936 MULTI: primary virtual IP for HPAHH;6007/109.41.8.81:38729: 192.168.77.42
Mon Oct 28 09:35:39 2019 us=587767 HPAHH;6007/109.41.8.81:38729 PUSH: Received control message: 'PUSH_REQUEST'
Mon Oct 28 09:35:39 2019 us=587874 HPAHH;6007/109.41.8.81:38729 SENT CONTROL [HPAHH;6007]: 'PUSH_REPLY,route-gateway 192.168.77.1,topology subnet,ping 60,ping-restart 360,ifconfig 192.168.77.42 255.255.255.0,peer-id 2' (status=1)
Mon Oct 28 09:41:41 2019 us=927974 109.41.8.81:33437 VERIFY OK: depth=0, C=DE, ST=YYY, O=XXX, OU=TS-BAN, CN=HPAHH;6007
Mon Oct 28 09:41:42 2019 us=166104 109.41.8.81:33437 [HPAHH;6007] Peer Connection Initiated with [AF_INET]109.41.8.81:33437
Mon Oct 28 09:41:42 2019 us=166317 MULTI: new connection by client 'HPAHH;6007' will cause previous active sessions by this client to be dropped.  Remember to use the --duplicate-cn option if you want multiple clients using the same certificate or username to concurrently connect.
Mon Oct 28 09:41:42 2019 us=166412 MULTI: Learn: 192.168.77.42 -> HPAHH;6007/109.41.8.81:33437
Mon Oct 28 09:41:42 2019 us=166430 MULTI: primary virtual IP for HPAHH;6007/109.41.8.81:33437: 192.168.77.42
Mon Oct 28 09:41:44 2019 us=266029 HPAHH;6007/109.41.8.81:33437 PUSH: Received control message: 'PUSH_REQUEST'
Mon Oct 28 09:41:44 2019 us=266148 HPAHH;6007/109.41.8.81:33437 SENT CONTROL [HPAHH;6007]: 'PUSH_REPLY,route-gateway 192.168.77.1,topology subnet,ping 60,ping-restart 360,ifconfig 192.168.77.42 255.255.255.0,peer-id 0' (status=1)
Mon Oct 28 09:53:44 2019 us=456137 HPAHH;6007/109.41.8.81:33437 [HPAHH;6007] Inactivity timeout (--ping-restart), restarting
Mon Oct 28 09:53:44 2019 us=456218 HPAHH;6007/109.41.8.81:33437 SIGUSR1[soft,ping-restart] received, client-instance restarting
Mon Oct 28 10:23:15 2019 us=882337 109.41.7.79:37186 VERIFY OK: depth=0, C=DE, ST=YYY, O=XXX, OU=TS-BAN, CN=HPAHH;6007
Mon Oct 28 10:23:16 2019 us=54203 109.41.7.79:37186 [HPAHH;6007] Peer Connection Initiated with [AF_INET]109.41.7.79:37186
Mon Oct 28 10:23:16 2019 us=54252 HPAHH;6007/109.41.7.79:37186 MULTI_sva: pool returned IPv4=192.168.77.42, IPv6=(Not enabled)
Mon Oct 28 10:23:16 2019 us=54318 HPAHH;6007/109.41.7.79:37186 MULTI: Learn: 192.168.77.42 -> HPAHH;6007/109.41.7.79:37186
Mon Oct 28 10:23:16 2019 us=54336 HPAHH;6007/109.41.7.79:37186 MULTI: primary virtual IP for HPAHH;6007/109.41.7.79:37186: 192.168.77.42
Mon Oct 28 10:23:18 2019 us=469115 HPAHH;6007/109.41.7.79:37186 PUSH: Received control message: 'PUSH_REQUEST'
Mon Oct 28 10:23:18 2019 us=469230 HPAHH;6007/109.41.7.79:37186 SENT CONTROL [HPAHH;6007]: 'PUSH_REPLY,route-gateway 192.168.77.1,topology subnet,ping 60,ping-restart 360,ifconfig 192.168.77.42 255.255.255.0,peer-id 0' (status=1)

TinCanTech

Your server administrator is the person who can fix this.

And I suspect you are using an old and unsupported version of openvpn on your server.

dualsbiker

Ok, and just theoretically the server admin is not that well versed ... What can he do ? (It's not me 🙂)
The OpenVPN version is 2.4.4

TinCanTech

dualsbiker wrote the server admin is not that well versed ... What can he do ?

Check the server log.

dualsbiker

Ok, I made a workaround. I wrote a script that checks the present of the tun0 interface and if it breaks I restart the clients OpenVPN service and then it reconnects.
Any ideas?

TinCanTech

dualsbiker wroteAny ideas?

Try this:
https://forums.openvpn.net/viewtopic.php?f=30&t=22603#p68963

But the fact is, your server admin is the only person who can help you.