Similar to this post RUT301 comm between PLC's in different subnets, I am looking to communicate across subnets. I bought a RUT301 thinking it would be the solution I needed, but now I’m not so sure. Do I have the right tool for the job?
Below is the test scenario using an RUT301 and a simple 5 port switch.
I have a local test scenario set up where laptop router are on default subnet, 192.168.1.x mask 255.255.255.0.
Looking to communicate to a Tridium Jace at IP 10.65.93.229 mask 255.255.255.192 gw10.65.93.193. End goal modbus tcp across port 502.
Test setup isn’t apples to apples but I was hoping by doing this I could simulate, and learn, prior to going back on site. Below is the real world problem I am looking to resolve at a customer site. I don’t know the overall network architecture, I just know the subnet info and that there is a single network connection where i can access these subnets by changing the IP of my laptop.
Current access and bulk of my communication is on subnet 10.65.92.0 mask 255.255.255.128 gw10.65.92.1
Need to pull in modbus tcp (port 502) data from subnet 10.65.93.192/26 mask 255.255.255.192 gw10.65.93.193 and also subnet 10.65.65.129/25 mask 255.255.255.128 gw10.65.65.129
I’d appreciate any assistance that could guide me to a solution. Cheers!
After reviewing your thread a few more times, I’d like to request a topology that would include these IP addresses with a clear showing of how everything is connected to what, and what external devices (switches, etc.) you have.
This will make it a lot easier to give an example of how you should be configuring your settings and such.
I don’t know the extent of the network architecture but the above is a simplistic version. The bulk of monitored devices communicate on 10.10.1.0 subnet. From my laptop/local access switch, I can communicate with all devices if I re-configure the laptop IP to the respective subnets individually. I need to be able to actively communicate to subnets 10.10.10.0 and 10.10.20.0 from 10.10.1.0 in order to monitor all downstream devices.
I’ve sent you a form to fill out so we can continue our conversation in private, to avoid accidentally leaking any sensitive information. In the Ticket ID field, simply enter the thread’s number, which is 14612.
In my scenario, I don’t have the ability to reconfigure the gateway. To overcome that, I had to set a basic NAT rule with the Action “Masquerade”.
This was a successful bench test based on a real world application, which I have yet to validate. I will provide an update if this does NOT resolve my issue.
Hi there, @Chasing_Time , thanks for keeping us updated in regards to your situation.
I’ll send you an e-mail (since you filled out the form) just in case, so you can reply to it if any further assistance would be needed, or alternatively, you can ask any questions here as well.
