Hello! first post! Trying to use the RIO with port forwarding so my OPC client connected to ETH1 (10.131.16.202) can talk to my OPC server (wago PLC 10.0.0.202:4840) connected to ETH0, however the firewall rules are not being saved, and the port 14840 in ETH1 remains closed.
Static IP on both ETH0 10.0.0.200 and ETH1 10.131.16.200
When I test the port on ETH0 it looks good (OPEN) Host 10.0.0.200:4840.
But not on the ETH1 side -port is closed or the request timed out- on Host 10.131.16.200:14840.
I then tried to make a firewall rule to open that port 14840, but there’s nothing in the firewall rules after I saved; even though it says it’s being saved:
Think of port forwarding from the client to the server (inbound). The external interface and port would be the port the client connects to. If I understand what you are attempting, the external port would be 14840 on external interface eth1 which redirects to your server at 10.0.0.202 at redirect port 4840 on eth0 (Basically the reverse of what you have in your screenshot).
Hi Philip, thanks for the reply, I tried it and when I test TCP port on ETH1 10.131.16.200:14840 it still displays port is closed…and when I try opc.tcp://10.131.16.200:14840 with UA expert on my laptop, I have a timeout on the comms.
That looks correct. Remove any firewall rules you may have setup that pertain to this - they are not needed and maybe they are causing issues.
How are you checking if the port is open or closed?
Also, it appears that OPC UA servers respond with a endpoint with the local address, which the client may see and then try to use, and then fail to connect since it is unreachable. You may not be able to work around that. NAT doesn’t work in all scenarios - it is a hack.
