Unavailable docker TCP ports

Hardware and Linux
, ,
1

Hi everyone!

I am currently having an issue with PFC200 and exposed ports.

Upon bootup, two docker containers start successfully and are forwarded to ports:

  • Node-RED 0.0.0.0:1880->1880/tcp, 0.0.0.0:8090->8090/udp
  • InfluxDB 0.0.0.0:8086->8086/tcp, 0.0.0.0:8089->8089/udp

After a short while, external device (laptop) can easily connect to both ports.

Problem starts when ethernet connection is disturbed (by pulling a cable out) and reestablishing connection. Ports are still exposed and I have checked that processes on PLC are still running, but external device cannot connect to containers anymore given exposed ports. Restarting containers doesn’t fix the issue - the only way to fix it is to reboot controller.

I have checked and clear IPtables which also doesn’t solve the issue.

All other services like wbm or codesys visualisation work just fine.

Both containers are part of user-defined network with bridge model and fixed IP addresses within it.

I am trying to understand why is this happening - has anyone came across this before or have an idea what could be an issue?

Kind regards,

Marcin

2

Please see this post:

https://www.wago.community/t/ipv4-forwarding-in-pfc200/437

3

Thank you Kurt for a prompt reply,

First I was certain ipv4 forwarding was enabled when running command:

sysctl net.ipv4.ip_forward

image

But then followed your advise on checking conf file itself:

nano /etc/sysctl.conf

and there it is, set to 0!

image

Seems like every day is a school day :slight_smile:

Thank you