• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Docker exposed port don't send data on eth0
#1
Hello Armin,

I have an issue, that is hard to descript. 

Base is a NIOT-E-TPI51-EN-RE.
Eth0 is configured as DHCP and working, I can connect to the Portainer and Control Panel from the outer netwerk to this IP-Address
On this box Docker is enabled
First Container is a hilschernetpi/netpi-netx-ethernet-lan image, which enables the cifx0 as 'normal' Ethernet-Port.

cifx0 is configured as
- IP-Address: 192.168.1.1
- SUBNET: 255.255.255.0
- Gateway: 192.168.1.1
- DNS: 9.9.9.9

In the Docker a second Container which if from image hilschernetpi/netpi-raspbian is running a node script to build a OPC UA server.
This Container exposes the following ports
remote 2222: local 22 --> SSH
remote 4334: local4334 --> opc.tcp

I can access the SSH port of the second container (2222) from eth0 and cifx0 without any problems
opc.tcp (4334) is available from cifx0, but if I try to connect from eth0 I cannot get a connection. A ping on that port is working, but i don't get data.

Firewall settings
eth0: NAT-Trusted
cifx0: Trusted (default)

Routes:
- no routes defined -

I do not see the error, but I'm sure it is just in front of my eyes.

Can you give me a hint?

Kind regards,

Carsten
  Reply
#2
Well Carsten,

have you analyzed the telegrams on eth0 side with wireshark? Do you see your opc.tcp telegrams coming to eth0 and what are the responses of netPI on these requests? Doesn't it answer at all to these requests, or with a reply error or anything?

This is the first thing I would try.

All the rest I have in mind is just speculation.

Regards
Armin
Armin
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply
#3
Hello Armin, 

it was a old known opponent:

hilschernetpi/netpi-netx-ethernet-lan:latest

after I took:

hilschernetpi/netpi-netx-ethernet-lan:1.1.1

everything is fine.

But, this time, the boc has the actual firmware: NIOT-E-TPI51-EN-RE | V1.2.2.0

I don't know why, but on my boxes, an newer version of the cifx-enabler does not work.

Kind regards,

Carsten
  Reply
#4
Well the container hilschernetpi/netpi-netx-ethernet-lan:xxx writes to a log file during startup. Maybe we can get out some informations why hilschernetpi/netpi-netx-ethernet-lan:xxx containers > version 1.1.1 do not run on your devices.

The log file by the way you can watch yourself in the Docker management web tool in the containers overiew list using the icon "logs" as one of the 4 available icons per container.

Thx
Armin
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  USB Port Mapping DSongra 3 146 August-24th-2021, 10:57 AM
Last Post: Armin@netPI
  REST API server data communication MGharat 2 416 July-21st-2021, 07:01 AM
Last Post: MGharat
  Docker not enabled tad 10 747 July-14th-2021, 08:54 AM
Last Post: Armin@netPI
  Touchscreen with DVI Port Dipro 1 369 March-23rd-2021, 09:46 PM
Last Post: Armin@netPI
  requirement : reading of ethrnet/ip data & storing MGharat 6 1,104 February-1st-2021, 08:07 AM
Last Post: Armin@netPI
  Docker amd64 instead of arm biancode 3 730 January-17th-2021, 09:40 PM
Last Post: Armin@netPI
  docker.service start failed EUROKEY 13 3,136 January-17th-2021, 07:52 PM
Last Post: Armin@netPI
  Data logger Jan 11 2,152 October-14th-2020, 03:43 PM
Last Post: Jan
  Accessing a modbus device connected to RTE port from Node-RED tad 10 2,760 October-2nd-2020, 07:21 AM
Last Post: Armin@netPI
  5 x NL 50-Mpi and Node Red like colector data? Jotarod 4 1,172 September-14th-2020, 01:59 PM
Last Post: Armin@netPI

Forum Jump:


Users browsing this thread: 1 Guest(s)