# Ignition access to subnetwork PLC **URL:** \ **Category:** Ignition\ **Created:** [January 18, 2023, 10:55pm UTC](https://forum.inductiveautomation.com/t/ignition-access-to-subnetwork-plc/68762 "2023-01-18T22:55:58Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Nick\_Heiting](https://avatars.discourse-cdn.com/v4/letter/n/8797f3/32.png) [@Nick\_Heiting](https://forum.inductiveautomation.com/u/Nick_Heiting)\ **Post date:** [January 18, 2023, 10:55pm UTC](https://forum.inductiveautomation.com/t/ignition-access-to-subnetwork-plc/68762/1 "2023-01-18T22:55:58Z")
I have a networking maze that I am trying to navigate. I have Ignition communicating with a Rockwell PLC at 172.16.x.x. This PLC has a processor in slot 0 and everything is working as expected. On the backplane there is an ethernet module in slot 3. This module communicates to 8 different Rockwell PLCs at 192.168.10.x. to 192.168.80.x I can create a connection to the ethernet module in slot 3 and am able get status information from the module. I'm looking to create a connection to the PLCs through this module to reach the 192.168.x.x addresses. I feel like it should be possible through the connectionPath parameter but when I try this I only seem to be able to reach the ethernet module. I am trying to follow this guide without success. [https://docs.inductiveautomation.com/display/DOC80/Allen-Bradley+Connection+Paths](https://docs.inductiveautomation.com/display/DOC80/Allen-Bradley+Connection+Paths) - In my main plc on the 172 network I have a series of msg instructions to pull data using a CIP data table read with a path of: IO\_Network, 2, 192.168.80.10, 1, 0 where IO\_Network is the slot 3 from above. I could expand this stepping stone method to add the additional data I want but it would be more organized and straight-forward to establish a device connection path to each end unit. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [January 18, 2023, 11:05pm UTC](https://forum.inductiveautomation.com/t/ignition-access-to-subnetwork-plc/68762/2 "2023-01-18T23:05:20Z")
What model ethernet cards? (Asking because the 1756-ENET and 1756-EWEB cannot do the bridging you want, IIRC.) What have you tried for connection paths? I would expect it to be something like `1,3,2,192.168.x.y` or `1,3,2,192.168.x.y,1,0`. The '2' in the 3rd position might need to be a '3' or a '4', depending on the DLR/dual-IP options on the ethernet card in slot 3. ---
**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\ **Post date:** [January 18, 2023, 11:07pm UTC](https://forum.inductiveautomation.com/t/ignition-access-to-subnetwork-plc/68762/3 "2023-01-18T23:07:47Z")
Your other option would be to bridge from one network to the other with a multi-NAT firewall router. With this you could set up a NAT rule for each WAN address to pass you through to the LAN address of the other PLCs. You would have to consider what security risks this would introduce - if any - and apply firewall rules accordingly. ---
**Author:** ![Nick\_Heiting](https://avatars.discourse-cdn.com/v4/letter/n/8797f3/32.png) [@Nick\_Heiting](https://forum.inductiveautomation.com/u/Nick_Heiting)\ **Post date:** [January 19, 2023, 3:33pm UTC](https://forum.inductiveautomation.com/t/ignition-access-to-subnetwork-plc/68762/4 "2023-01-19T15:33:44Z")
Thank you pturmel. 1,3,2,192.168.x.y did the trick. My previous attempts used numerous different combinations but all ended in 192.168.x.y,1,0. My plc msg instruction always included the ending ",1,0" since I thought it needed to know to go to slot 0 of the final destination. For reference it is a 1756-EN3TR card.