# Gateway Redundancy - Device Connection Local Address

**URL:** <https://forum.inductiveautomation.com/t/gateway-redundancy-device-connection-local-address/117825>\
**Category:** General Discussion\
**Tags:** gateway\
**Created:** [November 12, 2026, 9:45pm UTC](https://forum.inductiveautomation.com/t/gateway-redundancy-device-connection-local-address/117825 "2026-11-12T21:45:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Christian\_Reynolds](https://avatars.discourse-cdn.com/v4/letter/c/e8c25b/32.png) [@Christian\_Reynolds](https://forum.inductiveautomation.com/u/Christian_Reynolds)\
**Post date:** [November 12, 2026, 9:45pm UTC](https://forum.inductiveautomation.com/t/gateway-redundancy-device-connection-local-address/117825/1 "2026-11-12T21:45:46Z")

</div>

We have several machines that are clones of each other with the same IP addresses on the PLCs. To work around this, we have each machine connected to its own VLAN. On the OS that our gateway is running on (a VM in HyperV), we have multiple interfaces setup connecting to each of the VLANs with its own IP address. With that, we are utilizing the "Local Address" setting to point the gateway device connection to each specific interface for each machine.

We are working on setting up redundant gateways as we are becoming more reliant on Ignition. Trouble is, I cannot setup (or its not ideal) two gateway servers with interfaces that have the same IP address on the same network. On the backup gateway, I cannot configure a different "Local Address". What would be the best way to handle this?

---

<div class="post-metadata">

**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:** [November 12, 2026, 9:54pm UTC](https://forum.inductiveautomation.com/t/gateway-redundancy-device-connection-local-address/117825/2 "2026-11-12T21:54:04Z")

</div>

> [@Christian\_Reynolds](#):
>
> What would be the best way to handle this?

Adding same-subnet different-vlans as interfaces to any gateway, where the machine can see all of the subnet IPs, is not and cannot be a reliable networking setup. It simply breaks all OS cues for packet routing.

Consider using network namespaces to run simple containerized routers, exposing unique IPs on the gateway with 1:1 NAT into each distinct VLAN. Or install a product like Rockwell's NATR on each machine.

---

<div class="post-metadata">

**Author:** ![ryan.white](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan.white/32/73193_2.png) [@ryan.white](https://forum.inductiveautomation.com/u/ryan.white)\
**Post date:** [November 12, 2026, 10:15pm UTC](https://forum.inductiveautomation.com/t/gateway-redundancy-device-connection-local-address/117825/3 "2026-11-12T22:15:05Z")

</div>

> [@pturmel](#):
>
> Rockwell's NATR

This is the approach we used at my last company for our various machines. Skorpian, Antaira, and Phoenix Contact are some other companies that make NAT routers for this purpose.

---

<div class="post-metadata">

**Author:** ![Christian\_Reynolds](https://avatars.discourse-cdn.com/v4/letter/c/e8c25b/32.png) [@Christian\_Reynolds](https://forum.inductiveautomation.com/u/Christian_Reynolds)\
**Post date:** [November 13, 2026, 2:18pm UTC](https://forum.inductiveautomation.com/t/gateway-redundancy-device-connection-local-address/117825/4 "2026-11-13T14:18:14Z")

</div>

@pturmel and @ryan.white I will need to test both!
