ads-client in a Docker about ads-client HOT 9 CLOSED

In my tests and experience, the 48898 TCP port is the only one that is required.

It's important to understand that the 48898 is the port that the PLC/TwinCAT router is listening to. However the ads-client itself uses next available/random TCP port to connect from, unless set excplicitly to port with localTcpPort setting, as you have.

So if you set localTcpPort to like 34567, and you connect to target PLC's port 48898, you need to allow communication from docker 34567 -> PLC 48898. If you don't set localTcpPort, you need to allow all communication from docker -> PLC 48898.

Hope this message makes any sense.

from ads-client.

Hi,

Thanks for your Answer. This make sense, but it didn't work.
if i route the Port 48898/tcp (-p 48898:48898) in to the Container, it doesn't work.

Maybe it is different what the -p Parameter does in comparison to --network host Parameter..

Interestingly, the node-red-contrib-ads node works without port forwarding (Nor 48898). The connection is established as soon as the route is entered on the PLC.
Is there a difference in the connection in the Lib?

from ads-client.

Interesting. What happens if you set localAdsPort and localAddress empty?

Of course these are totally different libraries. Could you share all the settings from both?

from ads-client.

Sure:

IP's are not the same, only an example how it works.

If i set localAdsPort and localAddress empty, it doesn't work. It also doesn't work in --network host mode..
If i only leave localAddress empty, it works. Seems to be the localAdsPort is required..?

from ads-client.

Sorry.. I mean localTcpPort, not ads port. The ADS port is required as you are using Raspberry Pi without AMS router.

from ads-client.

same result:

from ads-client.

So both localAddress and localTcpPort are now empty?`

EADDRNOTAVAIL means that it can't start a connection from local interface 10.1.47.50.
https://www.google.com/search?q=eaddrnotavail+site:stackoverflow.com

from ads-client.

if both are empty, it seems to work!

Maybe, docker has a problem when localAddress is set, because of every container has it own ip.. ?
if these feelds are empty, it works, even without any port routing.
Great!

Maybe you can add this in your description..?
Thanks alot!

from ads-client.

Glad to hear! :)

The localAddress can be empty almost always. Only reason I can image is that you have many interfaces (like ethernet, wifi, etc) and you need to provide manually which one to use.

So the problem indeed was that it tried to connect using 10.1.47.50 however the was no such interface in your docker container.

I'll see if I could add this info somewhere in FAQ!

from ads-client.