RMS VPN - problem with connection

RobertDudzik · May 27, 2025, 7:25am

I try to use RMS VPN and I configure it with the manual;

My problem is that I can not ping any configured devices on the other side (I use TRB140).
My hub is working, TRB140 can ping my device (localy) but when I use OpenVPN tunel there is no connection.

Please help, I do not understand why there is no help from Teltonika, it is paid option!
Do they care ?

Adreses;
Client in hub have DHCP and hub have network 192.168.199.0 with mask 255.255.255.0
TRB140 LAN; 192.168.15.10 / 255.255.255.0 Routes in hub; 192.168.15.15/255.255.255.255

When I connect in hub/sesions I have adresses;
192.168.199.6 - device
192.168.199.10 - user

On my PC / TAP adapter DHCP

log from OpenVPN;

*Tue May 27 09:13:22 2025 Warning: route gateway is not reachable on any active network adapters: 192.168.199.9*
*Tue May 27 09:13:22 2025 Warning: route gateway is not reachable on any active network adapters: 192.168.199.9*
*Tue May 27 09:13:22 2025 SYSTEM ROUTING TABLE*
*Tue May 27 09:13:22 2025 0.0.0.0 0.0.0.0 192.168.0.1 p=0 i=17 t=4 pr=3 a=717 h=0 m=25/0/0/0/0*
*Tue May 27 09:13:22 2025 127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=7445 h=0 m=331/0/0/0/0*
*Tue May 27 09:13:22 2025 127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=7445 h=0 m=331/0/0/0/0*
*Tue May 27 09:13:22 2025 127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=7445 h=0 m=331/0/0/0/0*
*Tue May 27 09:13:22 2025 169.254.0.0 255.255.0.0 169.254.188.84 p=0 i=7 t=3 pr=2 a=2078 h=0 m=281/0/0/0/0*
*Tue May 27 09:13:22 2025 169.254.188.84 255.255.255.255 169.254.188.84 p=0 i=7 t=3 pr=2 a=2078 h=0 m=281/0/0/0/0*
*Tue May 27 09:13:22 2025 169.254.255.255 255.255.255.255 169.254.188.84 p=0 i=7 t=3 pr=2 a=2078 h=0 m=281/0/0/0/0*
*Tue May 27 09:13:22 2025 192.168.0.0 255.255.255.0 192.168.0.243 p=0 i=17 t=3 pr=2 a=717 h=0 m=281/0/0/0/0*
*Tue May 27 09:13:22 2025 192.168.0.243 255.255.255.255 192.168.0.243 p=0 i=17 t=3 pr=2 a=717 h=0 m=281/0/0/0/0*
*Tue May 27 09:13:22 2025 192.168.0.255 255.255.255.255 192.168.0.243 p=0 i=17 t=3 pr=2 a=717 h=0 m=281/0/0/0/0*
*Tue May 27 09:13:22 2025 192.168.4.0 255.255.255.0 192.168.4.55 p=0 i=9 t=3 pr=2 a=7439 h=0 m=281/0/0/0/0*
*Tue May 27 09:13:22 2025 192.168.4.55 255.255.255.255 192.168.4.55 p=0 i=9 t=3 pr=2 a=7439 h=0 m=281/0/0/0/0*
*Tue May 27 09:13:22 2025 192.168.4.255 255.255.255.255 192.168.4.55 p=0 i=9 t=3 pr=2 a=7439 h=0 m=281/0/0/0/0*
*Tue May 27 09:13:22 2025 192.168.117.0 255.255.255.0 192.168.4.55 p=0 i=9 t=3 pr=2 a=7439 h=0 m=281/0/0/0/0*
*Tue May 27 09:13:22 2025 192.168.117.77 255.255.255.255 192.168.4.55 p=0 i=9 t=3 pr=2 a=7439 h=0 m=281/0/0/0/0*
*Tue May 27 09:13:22 2025 192.168.117.255 255.255.255.255 192.168.4.55 p=0 i=9 t=3 pr=2 a=7439 h=0 m=281/0/0/0/0*
*Tue May 27 09:13:22 2025 192.168.118.0 255.255.255.0 192.168.4.55 p=0 i=9 t=3 pr=2 a=7439 h=0 m=281/0/0/0/0*
*Tue May 27 09:13:22 2025 192.168.118.78 255.255.255.255 192.168.4.55 p=0 i=9 t=3 pr=2 a=7439 h=0 m=281/0/0/0/0*
*Tue May 27 09:13:22 2025 192.168.118.255 255.255.255.255 192.168.4.55 p=0 i=9 t=3 pr=2 a=7439 h=0 m=281/0/0/0/0*
*Tue May 27 09:13:22 2025 224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=7445 h=0 m=331/0/0/0/0*
*Tue May 27 09:13:22 2025 224.0.0.0 240.0.0.0 169.254.188.84 p=0 i=7 t=3 pr=2 a=7442 h=0 m=281/0/0/0/0*
*Tue May 27 09:13:22 2025 224.0.0.0 240.0.0.0 192.168.4.55 p=0 i=9 t=3 pr=2 a=7442 h=0 m=281/0/0/0/0*
*Tue May 27 09:13:22 2025 224.0.0.0 240.0.0.0 192.168.0.243 p=0 i=17 t=3 pr=2 a=2243 h=0 m=281/0/0/0/0*
*Tue May 27 09:13:22 2025 255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=7445 h=0 m=331/0/0/0/0*
*Tue May 27 09:13:22 2025 255.255.255.255 255.255.255.255 169.254.188.84 p=0 i=7 t=3 pr=2 a=7442 h=0 m=281/0/0/0/0*
*Tue May 27 09:13:22 2025 255.255.255.255 255.255.255.255 192.168.4.55 p=0 i=9 t=3 pr=2 a=7442 h=0 m=281/0/0/0/0*
*Tue May 27 09:13:22 2025 255.255.255.255 255.255.255.255 192.168.0.243 p=0 i=17 t=3 pr=2 a=2243 h=0 m=281/0/0/0/0*
*Tue May 27 09:13:22 2025 SYSTEM ADAPTER LIST*
*Tue May 27 09:13:22 2025 Intel(R) 82574L Gigabit Network Connection*
*Tue May 27 09:13:22 2025   Index = 9*
*Tue May 27 09:13:22 2025   GUID = {478323E9-B4E6-4828-B3D3-23A7AEBE2B4D}*
*Tue May 27 09:13:22 2025   IP = 192.168.4.55/255.255.255.0 192.168.117.77/255.255.255.0 192.168.118.78/255.255.255.0 *
*Tue May 27 09:13:22 2025   MAC = 00:0c:29:c2:f7:ac*
*Tue May 27 09:13:22 2025   GATEWAY = 0.0.0.0/255.255.255.255 *
*Tue May 27 09:13:22 2025   DNS SERV =  *
*Tue May 27 09:13:22 2025 Intel(R) 82574L Gigabit Network Connection #2*
*Tue May 27 09:13:22 2025   Index = 17*
*Tue May 27 09:13:22 2025   GUID = {BE892940-9FE0-453C-99C1-7ACB0EC432C7}*
*Tue May 27 09:13:22 2025   IP = 192.168.0.243/255.255.255.0 *
*Tue May 27 09:13:22 2025   MAC = 00:0c:29:c2:f7:b6*
*Tue May 27 09:13:22 2025   GATEWAY = 192.168.0.1/255.255.255.255 *
*Tue May 27 09:13:22 2025   DHCP SERV = 192.168.0.1/255.255.255.255 *
*Tue May 27 09:13:22 2025   DHCP LEASE OBTAINED = 2025-05-27 09:01:23*
*Tue May 27 09:13:22 2025   DHCP LEASE EXPIRES  = 2025-06-03 09:01:23*
*Tue May 27 09:13:22 2025   DNS SERV = 192.168.0.11/255.255.255.255 8.8.8.8/255.255.255.255 *
*Tue May 27 09:13:22 2025 Wintun Userspace Tunnel*
*Tue May 27 09:13:22 2025   Index = 10*
*Tue May 27 09:13:22 2025   GUID = {5105517D-BC2C-424D-BB39-42EE556BB89C}*
*Tue May 27 09:13:22 2025   IP = 0.0.0.0/0.0.0.0 *
*Tue May 27 09:13:22 2025   MAC = *
*Tue May 27 09:13:22 2025   GATEWAY = 0.0.0.0/255.255.255.255 *
*Tue May 27 09:13:22 2025   DNS SERV =  *
*Tue May 27 09:13:22 2025 TAP-Windows Adapter V9*
*Tue May 27 09:13:22 2025   Index = 7*
*Tue May 27 09:13:22 2025   GUID = {315F91B1-05CD-4A57-A437-9194F8BA4D96}*
*Tue May 27 09:13:22 2025   IP = 169.254.188.84/255.255.0.0 *
*Tue May 27 09:13:22 2025   MAC = 00:ff:31:5f:91:b1*
*Tue May 27 09:13:22 2025   GATEWAY = 0.0.0.0/255.255.255.255 *
*Tue May 27 09:13:22 2025   DHCP SERV = 0.0.0.0/255.255.255.255 *
*Tue May 27 09:13:22 2025   DHCP LEASE OBTAINED = 2025-05-27 09:13:22*
*Tue May 27 09:13:22 2025   DHCP LEASE EXPIRES  = 2025-05-27 09:13:22*
*Tue May 27 09:13:22 2025   DNS SERV =  *
*Tue May 27 09:13:22 2025 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )*
*Tue May 27 09:13:21 2025 ERROR: Connection completed with critical errors.*

MatasR · May 27, 2025, 10:17am

Hello, Robert,

Looks to be an issue with the routes that you have set up under the Routes section in the RMS VPN Hub.

If I read it correctly, you have a route that looks like this:

I’ve marked the “Clients” selection, as some clients tend to select their RMS user instead of the device, which is incorrect. This needs to be your device.

Now if your route does look like the one in the image, then it’s incorrect. You are trying to reach a device that is under the .199 subnet, which in that case, your route needs to look like this:

The above example will allow you to reach any device within the .199 subnet.

If you wish to add a route to only reach that one address, then your route should look like this:

After you’ve set the routes up, you’ll have to restart your VPN Hub to apply these changes.

After doing so, ensure that your LAN forwarding option is enabled under the Routes tab:

Once that’s been done, you can try connecting to your VPN and try to reach your devices again.

If it still doesn’t end up working, another thing you can check is LAN Masquerading under the WebUI → Network → Firewall → Zones tab: TRB140 Firewall - Teltonika Networks Wiki

Once you’re there, ensure that the Masquerading option is Enabled:

Save & Apply the changes, and try to ping your end device once more.

For any other information related to RMS VPN Hubs, do check out this Wiki: RMS VPN Hubs - Teltonika Networks Wiki

Kind regards,
M.

RobertDudzik · May 27, 2025, 10:31am

Sorry but my device TRB140 is configured as bellow;
My LAN settings:

my zones settings

testing my TRB to device path

So that was device settings, now HUB VPN settings;

configuration;

Routes;

Clients;

So in my opinion you are not right, any sugestions, why I have errors ?

MatasR · May 27, 2025, 11:04am

As instructed in my previous message, kindly enable Masquerading as it is disabled, as seen in your screenshot:

Next, is there any particular reason why your Virtual Network IP address is set to 192.168.199.0 and not left at the default 192.168.255.0?

Here’s yours:

And here’s mine, the default for comparison:

I’ll be waiting for more information,
M.

RobertDudzik · May 27, 2025, 11:34am

I change the default network VPN from 192.168.199.0 to 192.168.255.0 because there was no reason to not to set default and turned on Masquerading:

and deleted forwarding from LAN

and it works, but I don’t understand why because manual said diffrent;

Manual

MatasR · May 27, 2025, 11:43am

Glad you’ve resolved it!

Generally, when I configure something on my own devices to test something out, I don’t even touch the Forwarding between zones settings, just leave them as they are and it ends up working just fine. More so, those instructions seem to be under LAN-To-LAN communication.

I’ll speak to the RMS team regarding the Wiki page to see if we can update the procedure to avoid confusion like this in the future.

Regards,
M.