Default Gateway does not work

[Armin@netPI]

Ok now I am able to see your screen shots.

When I am looking to your screen shot you made using the command

Code:

ip route show

 then I see a default gateway 169.254.100.97 which is pretty much the same as in your netPI's LAN settings page (screen shot 2). So this matches

So my expectation is like you that whenever you ping to 8.8.8.8 for example you are getting a reply instantly.

On the other hand you are telling me that you were able to pull the "hilscher debian container" which tells me also that the principle connection over your gateway works and also the DNS server must have been working correctly since pulling an image goes over the name https://registry-1.docker.io/v2/ internally always.

My netPI here in the office network receives its IP over a gateway/server too and I think this is the case in 99% of all applications I know of with netP. I tried the same like you ... loading the debian stretch container ... starting it with host mode setting.

Here is what I did

Code:

root@NTB827EBD50766:/# ip route show
default via 10.11.0.10 dev eth0 proto dhcp metric 100
10.11.0.0/16 dev eth0 proto kernel scope link src 10.11.5.13 metric 100
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
root@NTB827EBD50766:/# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=55 time=1.652 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=55 time=1.648 ms
^C--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.648/1.650/1.652/0.000 ms
root@NTB827EBD50766:/#

here it works as expected. Especially in "host mode" the container shares the TCP/IP stack of the host system so it runs 100% in the same context as the host ... and your host is able to pull images ... but the container is not able to ping an external IP address ... this really sounds weird to me and I defenitively cannot explain.

Thx
Armin