FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
+1 vote
2,059 views 1 comments
by
Hi,

I am trying to use a RUT240 as a VPN client to allow remote programming of industrial PLC. I have it almost configured but even though I can ping the RUT240, I can't ping anything behind it.

Topology as follows:

PLC: 192.168.1.10
RUT240: 192.168.1.1
RUT240 gets IP of 10.0.0.6 connected as a TUN client to my Synology NAS with OpenVPN Server

VPN connection goes via 4G.

OpenVPN server running inside of NAS: 10.0.0.1
NAS on a company network: 192.168.4.102
Main router connecting to Internet: 192.168.4.1

I have a openvpn.conf set to push "route 192.168.1.0 255.255.255.0", route 192.168.1.0 255.255.255.0, and I am using ccd and have ccd file with iroute "192.168.1.10"

I can ping 10.0.0.1 (VPN server), 192.168.4.102 (NAS), and 192.168.4.1 (main router) from RUT240 CLI.

I can ping 10.0.0.1 (VPN server), 192.168.4.102 (NAS), and 192.168.4.1 (main router) from laptop connected to RUT240 WiFi.

However, I have an issue from the other side:

I can ping 192.168.1.1 (RUT240) from anywhere in my company LAN, because I set route in my main router to direct 192.168.1.0 to my NAS which runs the vpn server.

I can't ping any other 192.168.1.X IP other than the RUT240 from my company LAN. Of course, I can ping the IPs from local network, as in from 192.168.1.20 to 192.168.1.10.

I was thinking that would be firewall, but after getting nowhere (even trying to open it completely) I would like to ask for help.

When I run tcpdump on RUT240 and try to ping 192.168.1.1 from 192.168.4.100, there is nothing in tcpdump, but pings return nicely.

When I run tcpdump on RUT240 and try to ping 192.168.1.10 from 192.168.4.100, tcpdump shows me:

IP 10.0.0.1 > 192.168.1.10: ICMP echo request, id 14226, seq 1, length 64
IP 10.0.0.1 > 192.168.1.10: ICMP echo request, id 14226, seq 2, length 64

but the pings on 192.168.4.100 time out. Any ideas? Thanks
by
Turns out, that if you don't set-up a gateway of 192.168.1.1 on the 192.168.1.10 device (which has static IP configuration AND the gateway setting is in a completely different part of the network settings), it doesn't know where to return the pings.

RUT240 was set-up perfectly fine.

Oh and beware, some shitty mobile network providers block higher ports, so I need to run my VPN Server over port 80 just in case.

1 Answer

0 votes
by anonymous
The IP that your RUT obtains from your VPN server needs to be different to the RUT's local LAN.

So if your RUT is obtaining 192.168.1.100 (as a client) from your VPN server, you'd need to set a non routable subnet on the RUT, like 10.0.0.1 for the RUT's clients.