Ok, I understand. Just a little background information as I think through how I want to ultimately configure this installation. For this setup we have three eWONs. Normally these stand alone and provide access to multiple devices on the LAN of the eWON. All the eWONs and all the devices for this installation currently reside on the same LAN.
Typically we use the cellular connection of an eWON to access the devices on its LAN, but the service in the area is poor, so we switched one of the eWONs to an Ethernet connection. Through this single eWON we can access all the devices on the LAN side, which normally would be sufficient, however…
…each eWON also runs a BASIC IDE routine which pushes data to a cloud from the PLC immediately local to the eWON. The first eWON with Ethernet connection to the internet obviously performs this function without issue, and it is using two topics to access two PLCs in its immediate locale, so only one topic remains to access the two PLCs located with the other two eWONs. The goal is to have those other two eWONs run the routine to push data from the PLCs at their locale to the internet through the first eWON. To do so, it sounds like the only solution is to move the LAN side of the other eWONs and the devices at their locale to a subnet separate from the LAN of the first eWON.
Changing the IP addresses can be done, and in the long run is probably the best solution.
I wanted to reason it out in writing to make sure I was on track.