The situation here is: we have an eWon Cosy 141. I have it set up on their network and in my eCatcher account, all that is working fine. They need to be able to FTP from their plant network into the PLC that is behind the eWon.
For another customer, I need that PLC to be able to send and receive SQL commands. I feel like any solution I reach for FTP could also be applied there.
I found this support article for the Cosy 131 that seems like a good solution: https://websupport.ewon.biz/sites/default/files/kb-0241-0-en_reach_a_device_behind_an_ewon_on_the_same_remote_site_but_from_two_different_networks.pdf
However, on the Cosy 141 I do not have this NAT 1:1 page in my Gateway wizard. When I go into the advanced COM settings, I see variables like NAT11In1 that seem to match the fields shown, but I’d need to know specifically what to change to mimic it, if the functionality exists. Also, is it possible for the Mapped IP I set up to be the same as the eWon’s WAN side IP? It would be nice if I didn’t have to use up two IPs on their network.
I also found an article for the 141 about just forwarding all traffic: https://websupport.ewon.biz/sites/default/files/kb-0068-0-en-access_internet_via_cosy_beside_talk2m_vpn_0.pdf
I guess the main reason I haven’t done this is the hope that the previous option could work with only one IP, because this option seems like both IPs would go on the network regardless. Also, there may be future machines where I have more than just the PLC on the internal LAN, and I would only want the PLC to get out. If the NAT won’t work out, I am willing to do this for now and get another model for such machines.
So if I could get instructions on how to achieve some sort of NAT or transparency where the PLC can get to the plant network and I only need to use up one IP, that would be great.
If not, and the traffic forwarding would work, I’ll go try that.
Thanks,
Corey