April-30th-2019, 01:17 PM
Hello Armin,
thank you for your post and help. Playing a little bit around with these things it seems to work sometimes via wifi. Sometimes it does not.
I need to further investigate and I will write here. Now I'm using the latest version of the hilschernetpi/netpi-netx-ethernet-lan/ container as a starting point.
During the process of standard gateway modifications via ip command I got also this message
I could fix that by log in as root and run
When I restart the NetPi and log into the container via ssh things look like this
With this configuration DNS does not work.
If I delete all default routes except the one for wlan0 in line 3 then it works when I have wifi connection.
Unfortunately with this configuration it does not work (Internet access through the router which has ip 192.168.0.1 and is connected to cifx0 via a switch):
I'm getting closer...
Best,
Andreas
thank you for your post and help. Playing a little bit around with these things it seems to work sometimes via wifi. Sometimes it does not.
I need to further investigate and I will write here. Now I'm using the latest version of the hilschernetpi/netpi-netx-ethernet-lan/ container as a starting point.
During the process of standard gateway modifications via ip command I got also this message
Code:
sudo: unable to resolve host NetPi1
I could fix that by log in as root and run
Code:
echo 127.0.0.1 computer_name >> /etc/hosts
When I restart the NetPi and log into the container via ssh things look like this
Code:
default via 192.168.0.1 dev cifx0
default via 192.168.0.1 dev eth0 proto static metric 100
default via 10.98.44.1 dev wlan0 proto static metric 600
10.98.44.0/22 dev wlan0 proto kernel scope link src 10.98.45.128 metric 600
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
192.168.0.0/24 dev cifx0 proto kernel scope link src 192.168.0.3
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.2 metric 100
If I delete all default routes except the one for wlan0 in line 3 then it works when I have wifi connection.
Unfortunately with this configuration it does not work (Internet access through the router which has ip 192.168.0.1 and is connected to cifx0 via a switch):
Code:
default via 192.168.0.1 dev cifx0
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
192.168.0.0/24 dev cifx0 proto kernel scope link src 192.168.0.3
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.2 metric 100
I'm getting closer...
Best,
Andreas