Question

I have a RUTXR1 with Firmware: RUTX_R_00.07.00

I successfully created an IPSEC VPN to a Watchguard firewall.

On the Watchguard side we have four subnets we should be able to route traffic to: 192.168.0.0/24, 192.168.50.0/24, 10.10.99.0/24 and 10.10.10.0/24 from the Teltonika.

Subnet 10.10.10.0/24 is not working, and that is because when I from a client behind the RUTXR1 try to reach this network the traffic doesn't route through the IPSEC tunnel I believe.

When doing a traceroute I get the following answers:

Tracing route to 192.168.0.8 over a maximum of 30 hops

  0  DESKTOP-B0G0ILD.lan [192.168.16.163]

  1  Teltonika-RUTXR1.com [192.168.16.1]

  2  192.168.0.1

  3  192.168.0.8

Tracing route to 192.168.50.8 over a maximum of 30 hops

  0  DESKTOP-B0G0ILD.lan [192.168.16.163]

  1  Teltonika-RUTXR1.com [192.168.16.1]

  2  192.168.0.1

  3  192.168.50.8

Tracing route to 10.10.99.6 over a maximum of 30 hops

  0  DESKTOP-B0G0ILD.lan [192.168.16.163]

  1  Teltonika-RUTXR1.com [192.168.16.1]

  2  192.168.0.1

  3   10.10.99.6

Tracing route to 10.10.10.6 over a maximum of 30 hops

  0  DESKTOP-B0G0ILD.lan [192.168.16.163]

  1  Teltonika-RUTXR1.com [192.168.16.1]

  2     *        *        *

When going to network 10.10.10.0 the traffic looks like it is not going through the tunnel.

Is subnet 10.10.10.0 blocked in RUTXR1? Or am I missing something?

Answer 1

I found the problem.

On the wathguard side, deep in the configuration on another old school BOVPN, the network 10.10.10.0/24 was routed to the same subnet set on the Teltonika RUTXR1.

Now everything is working and I have learned a lot about how the Teltonika works. Until now it has worked great with one exception that is: When changing any network related in it, it must to reboot...