Connecting local Ignition server to device on WAN side of StrideLinc

I have a mostly standalone piece of equipment that is supposed to help provide some additional cooling to a plants glycol system by utilizing waste heat generated by the equipment. I am having an issue with integrating the controls for a pump on the plant network with the local Ignition system on the equipment however.

The pump is controlled by a Productivity processor that controls a VFD to run the pump and a few sensors to monitor conditions. It is connected to the main plants Ignition system through Modbus TCP. The plant network uses a 10.10.xxx.xxx subnet.

The standalone equipment with the local Ignition server utilizes 192.168.xxx.xxx subnet on the other hand. It is currently integrated into the plant network using a StrideLinx NAT/VPN device, with the standalone equipment being on the LAN side and the plants network being on the WAN side. We can use the connection correctly going from the plant side to get into the standalone equipment.

However I need to get that Productivity processor on the local Ignition system, so the equipment operator can control the glycol pump as needed. I am unsure of how to set up this connection however.

Your easiest method may be to set up a gateway network between the 2 Ignition systems. This way, all the tags and data can be used by both systems without setting up multiple modbus connections to the PLC. You may need to open firewall ports depending on the setup (port forwarding), or going from LAN to WAN it might be able to make the connection without port forwarding, but that's just something you'll have to try.

Does the local Ignition have the StrideLinc set as its default gateway? Does the StrideLinc allow outbound traffic? On port 502?