RTE3 Use real time ethernet as "normal" ethernet interface - Printable Version +- Hilscher Community Forum (https://forum.hilscher.com) +-- Forum: netPI 3 - Docker featuring Industrial Raspberry Pi 3 platform (https://forum.hilscher.com/forum-1.html) +--- Forum: Software (https://forum.hilscher.com/forum-5.html) +--- Thread: RTE3 Use real time ethernet as "normal" ethernet interface (/thread-410.html) |
RE: RTE3 Use real time ethernet as "normal" ethernet interface - Andi - April-10th-2019 I was surprised as well, to see the adapter there. Quote:Just let me ask you this. Do you use the network mode "host" when you start your container? Yes, I am using "host" as network type. Quote:I made tests with the new container and set the ip settings via the environment variables. I set IP_ADDRESS to 192.168.0.1 and SUB_NETMASK to 255.255.255.0 and when I jump into the container with a shell and call "ip addr show" it says 192.168.0.1/24 as it should. I don't see the subnet mask misconfigured. When using "192.168.0.1" as IP_ADRESS, I get the expected behaviour with 255.255.255.0 as Subnetmask. But when I use "10.7.1.115" as IP-Adress, the subnetmask is setted wrongly to "255.0.0.0". What happens to you, if you use my configuration? Code: address 10.7.1.115 Thanks! Andi RE: RTE3 Use real time ethernet as "normal" ethernet interface - patrick - April-11th-2019 Hi Andi, the network mode "host" is not supported with this feature. Mapping into the host system leads to conflicts between the network manager of the host and that of the container. Excerpt from the Manual (https://github.com/HilscherAutomation/netPI-netx-ethernet-lan/blob/master/README.md): "Limitation ... Servicing the cifx0 interface is only possible in the container it was created. It is not available to the Docker host or to any other containers started. …" Best regards Patrick RE: RTE3 Use real time ethernet as "normal" ethernet interface - Andi - April-11th-2019 Hey Patrick, Quote:the network mode "host" is not supported with this feature. I have tried to use a user-defined-network using driver "bridge" and the pre-defined "bridge" network, but I get the same result as using network-type "host". The IP-Adress shown with "ip add show" is "10.7.1.115/8". Have you tried to use the following configuration and reached the expected behaviour? Code: address 10.7.1.115 Thanks, Andi RE: RTE3 Use real time ethernet as "normal" ethernet interface - Armin@netPI - April-12th-2019 I can confirm that I see the same result as you do with your settings. It needs further investigations why this happens. We have no explanations right now. RE: RTE3 Use real time ethernet as "normal" ethernet interface - Armin@netPI - April-12th-2019 Problem has been found. The github source code project as been updated. The DockerHub repository is triggered for an automatic update already. DockerHub will need time to build a new tag. Monitor the repo's tag site https://cloud.docker.com/repository/docker/hilschernetpi/netpi-netx-ethernet-lan/tags if there is a new tag pushed. Patiently wait. Thx Armin RE: RTE3 Use real time ethernet as "normal" ethernet interface - Andi - April-12th-2019 Thanks for the update! When using the following configuration: Code: IP_ADDRESS 10.7.1.115 I get these results now: Quote:1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 For me, it looks like something is still not right, cause the broadcast is "10.7.1.1" instead of "10.7.1.255"? Also, I cannot find the route of the standard gateway, when checking "ip route show": Quote:default via 172.18.0.1 dev eth0 Is this missing, or do I need to check somewhere else? Tanks, Andi RE: RTE3 Use real time ethernet as "normal" ethernet interface - Armin@netPI - April-12th-2019 Andi, I see that routing is not being set in the current code and that the broadcast address is calculated wrong. Code needs one further correction. Investigation unfortunately cannot happen before april 23. sorry RE: RTE3 Use real time ethernet as "normal" ethernet interface - Armin@netPI - April-14th-2019 I corrected the issue with the broadcast address offline. Can’t test it. The issue with the routing and missing gateway is still present and needs further investigation Thx RE: RTE3 Use real time ethernet as "normal" ethernet interface - Andi - April-15th-2019 Hey Armin, now I get the following error when trying to start up the container: Quote:/etc/init.d/entrypoint.sh: line 35: unexpected EOF while looking for matching `"' I found the error, therer are wrong kind of quotation marks in the bash-script in line 34: Quote: IFS=. read -r i1 i2 i3 i4 <<< "$IP_ADDRESS” could you please fix this? For the standard-gateway I will than wait until after easter. Thanks! Andi RE: RTE3 Use real time ethernet as "normal" ethernet interface - Armin@netPI - April-15th-2019 You are right. Have it corrected now. Dock hub is building the image right now |