I am trying to connect to a X90 module that is behind a firewall. I have redirected successfully port for web (80), ftp (21), and ANSL on 11169. It all works excepts for the ANSL 11169 port: connection to target fails even hough the redirection is correctly in place (tested with Test-NetConnection 10.X.Y.10 -Port 11169, where 10.X.Y.10 is the router/firewall IP.
I am setting the target router IP in AS 4.12, with the correct port number.
Is there anything else I need to know to make it work ?
ANSL online connection is a pure TCP-based communication on port 11169 (this port is default for “ANSL unsecured” but can be changed in the project).
So if Web and FTP is working, there must be some other issue then the protocol itself.
You wrote “redirected”, and some sentences later “target router IP”.
So I’m a bit confused: do you use Port Forwarding, or IP routing, and what’s the target router IP, is it the router (doing the port forwarding?) set as Default Gateway in the PLC?
Maybe you could explain a bit more your setup (including the network settings of the PLC), so that we get a better impression of it?
But as already said: HTTP, FTP and ANSL are all based on native TCP - so if one TCP connections works, all of them should do so…
Sorry for the delay, somehow notifications disappeared.
Here is the topology :
PC ↔ Router on Wireguard VPN external IP :10.100.0.10 local LAN IP 10.11.12.1
On the LAN, two X90 PLC have fixed IP addresses like 10.11.12.10 (plc1) and 10.11.12.11 (plc2)
The router redirects a few ports :
8000 <> http, 8001 <> websocket, 8021 <> ftp, 8169 <> ANSL to plc1 and
It looks like AS 4.12 Online toolbox is not showing all options. Looking at the XML and digging the web I found the /REPO and /PT options both refer to PLC port :
I can put whatever I want in /REPO, it will only work if I set /PT=8169 to match my needs.
AS Gui is not showing the /PT option, so I have to edit manually the XML and #bang :it connects !
If any of you as detailed info about this and whether this should be filed as a bug, let me know.
Best regards
I saw your response too late to answer directly, sorry.
Happy to hear that you already found the solution, maybe I can at least explain a bit more your correct findings:
Automation Studio 4.12 supports still the legacy protocol INA2000 (which is UDP based) an in parallel the actual protocol ANSL (TCP based).
The parameter /REPO is an INA2000 parameter, and is used to sets the INA UDP Port (default: 11159) where the PLC is listen to, when INA2000 is active
The parameter /PT is the ANSL parameter setting the TCP port where the ANSL server on the PLC is listening at (default: 11169).
the /REPO parameter could also be used for ANSL, but if the /PT parameter is configurerd /REPO is ignored for ANSL connections.
The /PT-Parameter is set in the section “Extra CPU settings”, as it’s inside PVI a CPU parameter → this column has to be activated (like some others also, for example Username, Password, SSL/TLS Configuration and so on which are just supported by ANSL) in the “Online → Settings” dialog.
It’s possible to do that by “rightclick on the headline” → Columns → Extra CPU settings
Thanks a lot Alexander, this further clarifies the doc that I had seen but fully grasp.
It looks to me the doc can be improved with the information you provided (extra CPU setings syntax)
I am not sure why the use or /REPO did not work as /PT. I suspect I edited cpu.pkg by hand and did not reload the project.
In all case, this fully clarifies the subject.
All the best,
