May-2nd-2019, 11:02 AM
Hey,
I get the same output now. The Problem that now occurs is that the "bridged" network mode is not working.
the IP-Adresses look like this:
As you can see, the eth0 is using an IP-Adress, which is located within the subnet of the Network-Bridge. The docker-network-bridge than connects this IP-Adress to the host's IP-Adress of this adapter.
The cifx0 adapter directly gets the IP-Adress, which shall be used for remote communication and not that of the internal Network-Bridge, which is right?
If I connect the netPi over a switch with another device within the same subnet, I cannot ping either the device from within netPi's container, nor the netPi from the device, using 10.7.1.115 as IP-Adress. Could it be that docker is somehow prohibiting the communication or that it gets stuck within the container?
Have you been able to ping another device using the cifx0-adapter?
Thanks,
Andi
I get the same output now. The Problem that now occurs is that the "bridged" network mode is not working.
the IP-Adresses look like this:
Code:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: cifx0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:02:a2:49:bb:d0 brd ff:ff:ff:ff:ff:ff
inet 10.7.1.115/24 brd 10.7.1.255 scope global cifx0
valid_lft forever preferred_lft forever
8: eth0@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:ac:12:00:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 172.18.0.2/16 brd 172.18.255.255 scope global eth0
valid_lft forever preferred_lft forever
As you can see, the eth0 is using an IP-Adress, which is located within the subnet of the Network-Bridge. The docker-network-bridge than connects this IP-Adress to the host's IP-Adress of this adapter.
The cifx0 adapter directly gets the IP-Adress, which shall be used for remote communication and not that of the internal Network-Bridge, which is right?
If I connect the netPi over a switch with another device within the same subnet, I cannot ping either the device from within netPi's container, nor the netPi from the device, using 10.7.1.115 as IP-Adress. Could it be that docker is somehow prohibiting the communication or that it gets stuck within the container?
Have you been able to ping another device using the cifx0-adapter?
Thanks,
Andi