Bridging client's network

Hi My previous threat was closed. I would like to fact check and ask if my deployment is workable.

My current design is as below. My SCADA is able to read all data. But my problem is when my PC is connected to client’s network. I cannot access my SCADA.

Hence, by concept I have drawed the design below. Can you help to confirm if it will work doing it this way? My RUT200 will act as a VPN server and “dumb” switch just to extend more network ports on client’s network.

Is this design possible?

Hello,

Sorry for the late response. Could you please confirm if you still need help with this setup? If so, could you please tell me if you can reach the RUT200 LAN IP (192.168.88.1) from your PC, or are you only able to reach the client’s network via your PC?

Best Regards,

Hi yes,
My PC basically cannot reach the 192.168.88.0/24 network at all.

I have tried another approach by making my main RUT200 fix on WAN/LAN IP as 10.55.11.25(Making it a dumb switch). Then I make my PC(10.55.11.70) and SCADA(10.50.11.20) site on the same 10.55.11.xx network.
By doing this, I can access all the units with exception of the RUT200 VPN Client(192.168.99.1).
My PC(10.55.11.70) still cannot access 192.168.99.1 after I try to do a L2tp static route in the main RUT200 to route to 192.168.99.0 but I still cannot access it from my PC.
But the funny thing is when I use the CLI in RUT200, I can ping 192.168.99.1 from RUT200(10.55.11.25).
What settings am I missing here?

Besides that, when my PC is connected to to the RUT200 Client with 192.168.99.20 IP, I can still ping and access my SCADA on 10.55.11.20 here with static route rules to 10.55.11.0.

Hello,

As I understand, you’ve made some changes to your configurations. Could you please share the current network topology, similar to what you provided before? This will help me understand all the device connections and their IP addresses to assist you further. Thank you!

Best Regards,

Hi Here you go,
this is the design that I tried to do. But it dont work.

My PC can ping everyone except 192.168.99.1 router.
But my PC/SCADA cannot reach 192.168.99.1.
But my RUT200 main, can ping 192.168.99.1 within its CLI.
But on RUT200 client, I can ping my pc/scada.

Did I miss anything?

Thank you for the topology and detailed configuration description!

If I understood correctly, you are trying to reach the local IP of the RUT200 (Client) and not the VPN IP. If so, please ensure that the RUT200 (Main) router has a proper route (in Network → Routing → Static Routes) to the 192.168.99.1:

  • Interface: L2TP
  • Target: Client LAN IP
  • IPv4 Gateway: Client L2TP VPN IP

Additionally, please check the firewall rules in the WebUI (Network → Firewall → General settings) on the main RUT200 router to ensure traffic from 10.55.11.0/24 to 192.168.99.0/24 is accepted. Similarly, on the client RUT200 router, ensure that incoming connections from the 10.55.11.0/24 network are accepted.

Please let me know how it goes!

Best Regards,

Hi Marija,
Yes Static route has been done too.

I need my PC/SCADA to be able to reach 192.168.99.1. Reason I want to use client’s network is because I can utilize their internet. Hence my M2M sim card would only be for my VPN.

In RUT200(Main) Static Route
L2TP
Target IP:192.168.99.0
maks: 255.255.255.0
gateway: 192.168.8.20
unicast

In RUT(Client) Static Route
L2tp
Target IP: 10.55.11.0
maks:255.255.255.0
unicast

I have forwarded my firewall on both ends. I have attached a troubleshoot file for you. Not sure if you are able to trace.

So now my ping will be as such. (PC/SCADA will always be on 10.55.11.xx range of IP)
PC/SCADA-> RUT200(main) , client backbone (ok)
PC/SCADA-> RUT200(client:192.168.99.1) (request timeout)

using CLI in RUT
RUT200(main) → PC, SCADA, client backbone , RUT200(client) (ok)
RUT(Client)-> PC,SCADA,clientbackbone, RUT200(main) (ok)

RUT200(MAIN)
troubleshoot-Teltonika-RUT200.com-2024-05-28.tar.gz (116.1 KB)

RUT200(Client)
troubleshoot-Teltonika-RUT200.com-2024-06-04.tar.gz (146.4 KB)

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