I am using a RUT240 device in our workshop, and trying to connect remotely via Open-VPN, using the “Teltonika RMS VPN Hub” (Teltonika_RMS_VPN_Setup_0.9.0.7-beta).
Now the VPN connection starts up ok, connecting the to remote LAN, and for some time I have access to all connnected devices (Simatic PLC, HMI, other), but every 30 seconds, sometimes after a few minutes, the VPN apapter “disappears” and restarts, interrupting all connections.
This happens using different Windows 10 and 11 computers, from different locations via different networks, in the same way.
Any idea what I could do ?
Many thanks in advance to all,
best regards,
Thomas.
Thank you for reaching out and providing detailed information about the issue.
To better understand the situation, could you please provide the OpenVPN logs from the RUT240 client side? These logs can be accessed in the router’s web interface under Services → VPN → OpenVPN → Client’s Logs section.
thanks for your message. Unfortunately I cannot see any “Client’s Logs” section at the OpenVPN section. The attached screenshot shows what I can see there:
Missing gateway in routes
Warnings about failing to parse routes (failed to parse/resolve route for host/network: 10.x.x.x) indicate that the configuration lacks a --route-gateway or --ifconfig parameter.
Inactivity and TLS handshake timeouts
Repeated “Inactivity timeout (–ping-restart)” and “TLS Error: TLS handshake failed” messages suggest connectivity issues or mismatched OpenVPN settings, leading to failed key exchanges and keepalives.
Interrupted system calls and SIGTERM
OpenVPN is receiving a SIGTERM, causing forced restarts and further instability.
Cipher fallback warning
A note appears about needing BF-CBC fallback if cipher negotiation fails, as OpenVPN 2.6.9 no longer defaults to BF-CBC.
11455 Wed Jan 15 17:22:22 2025 daemon.err openvpn(7hAxnE6B)[23940]: event_wait : Interrupted system call (fd=-1,code=4)
11456 Wed Jan 15 17:22:22 2025 daemon.notice openvpn(7hAxnE6B)[23940]: net_addr_ptp_v4_del: 192.168.255.6 dev tun_c_rms_7hAxn
11457 Wed Jan 15 17:22:22 2025 daemon.notice openvpn(7hAxnE6B)[23940]: /etc/openvpn/updown.sh tun_c_rms_7hAxn 1500 0 192.168.255.6 192.168.255.5 init
11458 Wed Jan 15 17:22:22 2025 daemon.notice openvpn(7hAxnE6B)[23940]: SIGTERM[hard,] received, process exiting
11464 Wed Jan 15 17:22:22 2025 daemon.notice openvpn(7hAxnE6B)[24759]: Note: --cipher is not set. OpenVPN versions before 2.5 defaulted to BF-CBC as fallback when cipher negotiation failed in this case. If you need this fallback please add ‘–data-ciphers-fallback BF-CBC’ to your configuration and/or add BF-CBC to --data-ciphers.
11465 Wed Jan 15 17:22:22 2025 daemon.notice openvpn(7hAxnE6B)[24759]: OpenVPN 2.6.9 arm-openwrt-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] [DCO]
11466 Wed Jan 15 17:22:22 2025 daemon.notice openvpn(7hAxnE6B)[24759]: library versions: OpenSSL 3.0.14 4 Jun 2024, LZO 2.10
11467 Wed Jan 15 17:22:22 2025 daemon.notice openvpn(7hAxnE6B)[24759]: DCO version: N/A
11468 Wed Jan 15 17:22:22 2025 daemon.warn openvpn(7hAxnE6B)[24759]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
11472 Wed Jan 15 17:22:22 2025 daemon.notice openvpn(7hAxnE6B)[24759]: TCP/UDP: Preserving recently used remote address: [AF_INET]3.69.106.81:36937
11473 Wed Jan 15 17:22:22 2025 daemon.notice openvpn(7hAxnE6B)[24759]: UDPv4 link local: (not bound)
11474 Wed Jan 15 17:22:22 2025 daemon.notice openvpn(7hAxnE6B)[24759]: UDPv4 link remote: [AF_INET]3.69.106.81:36937
11511 Wed Jan 15 17:23:22 2025 daemon.err openvpn(7hAxnE6B)[24759]: TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
11512 Wed Jan 15 17:23:22 2025 daemon.err openvpn(7hAxnE6B)[24759]: TLS Error: TLS handshake failed
11513 Wed Jan 15 17:23:22 2025 daemon.notice openvpn(7hAxnE6B)[24759]: SIGUSR1[soft,tls-error] received, process restarting
11517 Wed Jan 15 17:23:23 2025 daemon.warn openvpn(7hAxnE6B)[24759]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
11518 Wed Jan 15 17:23:23 2025 daemon.notice openvpn(7hAxnE6B)[24759]: TCP/UDP: Preserving recently used remote address: [AF_INET]3.65.167.143:36937
11519 Wed Jan 15 17:23:23 2025 daemon.notice openvpn(7hAxnE6B)[24759]: UDPv4 link local: (not bound)
11520 Wed Jan 15 17:23:23 2025 daemon.notice openvpn(7hAxnE6B)[24759]: UDPv4 link remote: [AF_INET]3.65.167.143:36937
11521 Wed Jan 15 17:23:23 2025 daemon.notice openvpn(7hAxnE6B)[24759]: [teltonika-vpn-7hAxnE6Baot5ysPs] Peer Connection Initiated with [AF_INET]3.65.167.143:36937
11522 Wed Jan 15 17:23:23 2025 daemon.notice openvpn(7hAxnE6B)[24759]: TUN/TAP device tun_c_rms_7hAxn opened
11523 Wed Jan 15 17:23:23 2025 daemon.notice openvpn(7hAxnE6B)[24759]: net_iface_mtu_set: mtu 1500 for tun_c_rms_7hAxn
11524 Wed Jan 15 17:23:23 2025 daemon.notice openvpn(7hAxnE6B)[24759]: net_iface_up: set tun_c_rms_7hAxn up
11525 Wed Jan 15 17:23:23 2025 daemon.notice openvpn(7hAxnE6B)[24759]: net_addr_ptp_v4_add: 192.168.255.6 peer 192.168.255.5 dev tun_c_rms_7hAxn
11526 Wed Jan 15 17:23:23 2025 daemon.notice openvpn(7hAxnE6B)[24759]: /etc/openvpn/updown.sh tun_c_rms_7hAxn 1500 0 192.168.255.6 192.168.255.5 init
11527 Wed Jan 15 17:23:23 2025 daemon.notice openvpn(7hAxnE6B)[24759]: Initialization Sequence Completed
11573 Wed Jan 15 17:23:38 2025 daemon.notice openvpn(7hAxnE6B)[24759]: [teltonika-vpn-7hAxnE6Baot5ysPs] Inactivity timeout (–ping-restart), restarting
11574 Wed Jan 15 17:23:38 2025 daemon.notice openvpn(7hAxnE6B)[24759]: net_addr_ptp_v4_del: 192.168.255.6 dev tun_c_rms_7hAxn
11575 Wed Jan 15 17:23:38 2025 daemon.notice openvpn(7hAxnE6B)[24759]: /etc/openvpn/updown.sh tun_c_rms_7hAxn 1500 0 192.168.255.6 192.168.255.5 init
11576 Wed Jan 15 17:23:38 2025 daemon.notice openvpn(7hAxnE6B)[24759]: SIGUSR1[soft,ping-restart] received, process restarting
11606 Wed Jan 15 17:23:39 2025 daemon.warn openvpn(7hAxnE6B)[24759]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
11607 Wed Jan 15 17:23:39 2025 daemon.notice openvpn(7hAxnE6B)[24759]: TCP/UDP: Preserving recently used remote address: [AF_INET]3.65.167.143:36937
11608 Wed Jan 15 17:23:39 2025 daemon.notice openvpn(7hAxnE6B)[24759]: UDPv4 link local: (not bound)
11609 Wed Jan 15 17:23:39 2025 daemon.notice openvpn(7hAxnE6B)[24759]: UDPv4 link remote: [AF_INET]3.65.167.143:36937
11610 Wed Jan 15 17:23:39 2025 daemon.notice openvpn(7hAxnE6B)[24759]: [teltonika-vpn-7hAxnE6Baot5ysPs] Peer Connection Initiated with [AF_INET]3.65.167.143:36937
11611 Wed Jan 15 17:23:39 2025 daemon.notice openvpn(7hAxnE6B)[24759]: TUN/TAP device tun_c_rms_7hAxn opened
11612 Wed Jan 15 17:23:39 2025 daemon.notice openvpn(7hAxnE6B)[24759]: net_iface_mtu_set: mtu 1500 for tun_c_rms_7hAxn
11613 Wed Jan 15 17:23:39 2025 daemon.notice openvpn(7hAxnE6B)[24759]: net_iface_up: set tun_c_rms_7hAxn up
11614 Wed Jan 15 17:23:39 2025 daemon.notice openvpn(7hAxnE6B)[24759]: net_addr_ptp_v4_add: 192.168.255.6 peer 192.168.255.5 dev tun_c_rms_7hAxn
11615 Wed Jan 15 17:23:39 2025 daemon.notice openvpn(7hAxnE6B)[24759]: /etc/openvpn/updown.sh tun_c_rms_7hAxn 1500 0 192.168.255.6 192.168.255.5 init
11616 Wed Jan 15 17:23:40 2025 daemon.notice openvpn(7hAxnE6B)[24759]: Initialization Sequence Completed
The virtual tunnel interface type should indeed be TUN, so everything seems correct on that end. I’ve tested a setup similar to what you described. Could you try (if you haven’t already) updating the RUT240 client’s configuration and certificates?
If you haven’t done so already, you may also try restarting the VPN Hub to see if it makes any difference.
If the issue persists, I’d like to investigate further. I’ve sent you a form to fill out. Please use “11758” as the ticket ID when completing it. Once submitted, we’ll contact you privately to proceed with further investigation and troubleshooting.
thanks for your message. Looks like I got it sorted now. This is what I did:
1.) Firmware upgrade on my RTU240 (from RUT2_R_00.07.06.16 to RUT2_R_00.07.06.17).
2.) Delete the VPN hub from RMS. Also delete the corresponding “OpenVPN client” from the device.
3.) Set up a new VPN hub, with client, routes. (So that it looked like before.)
