RMS Client connection issues

Teltonika Networks
1

This has suddenly started to appear in my logs and I’m having multiple RMS user configs that are failing to connect. System has been stable for a year now and I’ve made no changes other than expanding from 39 devices to 86.

2024-05-01 15:57:28 --cipher is not set. Previous OpenVPN version 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.
2024-05-01 15:57:28 OpenVPN 2.5.7 Windows-MSVC [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on May 27 2022
2024-05-01 15:57:28 Windows version 10.0 (Windows 10 or greater) 64bit
2024-05-01 15:57:28 library versions: OpenSSL 1.1.1o  3 May 2022, LZO 2.10
2024-05-01 15:57:28 TCP/UDP: Preserving recently used remote address: [AF_INET]34.230.227.9:37698
2024-05-01 15:57:28 UDP link local: (not bound)
2024-05-01 15:57:28 UDP link remote: [AF_INET]34.230.227.9:37698
2024-05-01 15:57:29 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1541', remote='link-mtu 1542'
2024-05-01 15:57:29 WARNING: 'comp-lzo' is present in remote config but missing in local config, remote='comp-lzo'
2024-05-01 15:57:29 [teltonika-vpn-B59SIgexOFAhzMjp] Peer Connection Initiated with [AF_INET]34.230.227.9:37698
2024-05-01 15:57:29 OpenVPN ROUTE: OpenVPN needs a gateway parameter for a --route option and no default was specified by either --route-gateway or --ifconfig options
2024-05-01 15:57:29 OpenVPN ROUTE: failed to parse/resolve route for host/network: 192.168.255.0
2024-05-01 15:57:29 OpenVPN ROUTE: OpenVPN needs a gateway parameter for a --route option and no default was specified by either --route-gateway or --ifconfig options
2024-05-01 15:57:29 OpenVPN ROUTE: failed to parse/resolve route for host/network: 192.168.1.89
2024-05-01 15:57:29 OpenVPN ROUTE: OpenVPN needs a gateway parameter for a --route option and no default was specified by either --route-gateway or --ifconfig options
2024-05-01 15:57:29 OpenVPN ROUTE: failed to parse/resolve route for host/network: 192.168.1.88
2024-05-01 15:57:29 OpenVPN ROUTE: OpenVPN needs a gateway parameter for a --route option and no default was specified by either --route-gateway or --ifconfig options
2024-05-01 15:57:29 OpenVPN ROUTE: failed to parse/resolve route for host/network: 192.168.1.87
2024-05-01 15:57:29 OpenVPN ROUTE: OpenVPN needs a gateway parameter for a --route option and no default was specified by either --route-gateway or --ifconfig options

Do I need to specify the gateway in every client config now? Wondering what’s changed.

3

Hello,

To fix the routing issue, ensure each client config includes route information with the appropriate gateway specified. For example:

route 192.168.255.0 255.255.255.0 192.168.1.1
route 192.168.1.89 255.255.255.255 192.168.1.1
route 192.168.1.88 255.255.255.255 192.168.1.1
route 192.168.1.87 255.255.255.255 192.168.1.1

Replace 192.168.1.1 with your Teltonika device’s LAN gateway. This ensures proper routing for OpenVPN connections.

Please let me know if you need further assistance.

Best Regards,

4

This topic was automatically closed after 15 days. New replies are no longer allowed.