Ewon Cosy Port Forwarding

kyle wertheim

• February 12, 2024 18:44

We are trying to get an AB PLC to port forward from the LAN to our WAN. From previous research these are the current settings I have enabled in the Setup->Storage->Edit COM cfg

Proxy Enabled:1

ProxyExtItf: 0

ProxyProto1: 2

ProxySide1: 1

ProxyPort1: 44818

ProxySrvPort1: 44818

ProxySrvIPAddr1: 192.168.200.130

ProxyProto2: 2

ProxySide2: 2

ProxyPort2: 44818

ProxySrvPort2: 44818

ProxySrvIPAddr2: 192.168.200.130

ProxyProto3: 1

ProxySide3: 1

ProxyPort3: 44818

ProxySrvPort3: 44818

ProxySrvIPAddr3: 192.168.200.130

ProxyProto4: 1

ProxySide4: 2

ProxyPort4: 44818

ProxySrvPort4: 44818

ProxySrvIPAddr4: 192.168.200.130

ProxyProto5: 2

ProxySide5: 1

ProxyPort5: 8080

ProxySrvPort5: 80

ProxySrvIPAddr5: 192.168.200.130

ProxyProto6: 2

ProxySide6: 1

ProxyPort6: 8080

ProxySrvPort6: 80

ProxySrvIPAddr6: 192.168.200.130

We have the http forwarding working because we are able to open the PLC web interface on 192.168.200.130:8080 in our URL. So we are confused why we are not able to connect to the PLC with the 44818 port enabled bi-directional on TCP and UDP. 

More Context: We communicate to the PLC from an ignition server that is configured to communicate to the PLC via port 44818.

1

• 

  kyle wertheim

  • February 12, 2024 19:22

  Also WANItfProt is 2.

  I see WanPxyPort was set to 8080, I changed it to 44818 and nothing changed.

  Also changed WANPxyMode to 10 and that didn't fix it either.

  0
• 

  Adalberto Rivera

  • February 13, 2024 15:48

  Any help will be much appreciated!

  0
• 

  Martin

  • February 16, 2024 03:49

  Hi kyle wertheim / Adalberto Rivera

  Can you elaborate on what you mean by "port forward from the LAN to our WAN" ? Are you trying to allow your PLC to reach the internet or some cloud server through the Cosy's WAN port?

  0
• 

  kyle wertheim

  • February 16, 2024 11:40

  There is a machine PLC on a local machine/Cell level on a 192.168 address. We are trying to reach it from our plant network 100.101, ie port forward. We are not able to NAT1:1 though. We use ignition to pull data from PLCs so we need to port forward the 44818 port of the PLC to get this comm

  0
• 

  Kyle Reynolds

  • February 19, 2024 15:55

  Hi Kyle, 

  Can you ping the PLC with the NAT 1:1? I have seen issues with routing certain Allen Bradley communications because they are using broadcast messages, which are not routable.

  See also: NAT 1:1 on the Flexy

   

  0

Please sign in to leave a comment.