Good point, I hadn't noticed this yet
This is a conflict between the wifi-hotspot and wired interface which confuses the dns.
I'm not sure whether this can be solved structural (anybody...?..)
When connecting the wifi interface to your local network it won't happen (main reason why I wasn't aware until now).
So that's one solution, but needs configuring you don't like for various good reasons.
A bypass is temporarily disabling the hotspot. This is my preference as internet access for samplerbox is seldom needed.
Code:
root@samplerbox:~# mount -o remount,rw /
root@samplerbox:~# systemctl disable autohotspot
Removed symlink /etc/systemd/system/multi-user.target.wants/autohotspot.service.
root@samplerbox:~# reboot
....login again.....
root@samplerbox:~# ping google.com
PING google.com (142.250.179.142) 56(84) bytes of data.
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=1 ttl=117 time=7.97 ms
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=2 ttl=117 time=7.36 ms
^C
--- google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 7.369/7.669/7.970/0.313 ms
root@samplerbox:~# mount -o remount,rw /
....do the things you need internet for.....
root@samplerbox:~# systemctl enable autohotspot
Created symlink from /etc/systemd/system/multi-user.target.wants/autohotspot.service to /etc/systemd/system/autohotspot.service.
root@samplerbox:~# reboot
Hope this is clear.. Hans
