I just had to restart the Fritzbox, and the problem ocurred again:
ssh: connect to host 192.168.178.92 port 22: No route to host
Power management should be disabled. Maybe the Pi doesn't automatically reconnect when the router restarts?
It's odd that although the Pi doesn't show up on the router's local network overview, I can still surf the web, but name resolving takes like 5 seconds.
Great, thank you, @PromoFaux! I'll change the title when I'm clear about what exactly is the issue.
On Topic:
I'm not in trouble at the moment. Not sure if you meant that I should only run any of these in that case. Here's what I get now:
pi@raspberrypi:~ $ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enxb827ebbf9bd6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
link/ether b8:27:eb:bf:9b:d6 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DORMANT group default qlen 1000
link/ether b8:27:eb:ea:ce:83 brd ff:ff:ff:ff:ff:ff
pi@raspberrypi:~ $ ip addr show
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
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enxb827ebbf9bd6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether b8:27:eb:bf:9b:d6 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether b8:27:eb:ea:ce:83 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.92/24 brd 192.168.178.255 scope global wlan0
valid_lft forever preferred_lft forever
inet6 fe80::5cc8:f41e:77d9:40f3/64 scope link
valid_lft forever preferred_lft forever
pi@raspberrypi:~ $ ip route show
default via 192.168.178.1 dev wlan0 src 192.168.178.92 metric 303
192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.92 metric 303
When in trouble, it could be complicated to get the outputs, because the Pi is running headless. But if necessary I can try to move the Pi to a more suitable position before I get in trouble.
Yes, linux-ehou is my PC.
Sorry, I'm a bit tired (it's late in Germany), confused my shells...
I'll run the latter three commands on the Pi through ssh and edit the above post.
192.168.178.92 is the Pihole. Could the returned address be 0.0.0.0 because I didn't install the graphical web interface (so it doesn't conflict with my NextcloudPi installation)?
Could you still post results from below one on Pi-hole ?
ip link show; ip addr show; ip route show
I dont know whats going on with the reconfigure option but it should have populated that "local.list" file with proper IP address instead of 0.0.0.0.
You could alter that file manually for time being and put in the proper IP addresses (both entries the same IP!).
Will need to restart dnsmasq to apply:
sudo service dnsmasq restart
Maybe the @Developers know how come you have 0.0.0.0 in that file ?
pi@raspberrypi:~ $ ip link show; ip addr show; ip route show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enxb827ebbf9bd6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
link/ether b8:27:eb:bf:9b:d6 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DORMANT group default qlen 1000
link/ether b8:27:eb:ea:ce:83 brd ff:ff:ff:ff:ff:ff
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
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enxb827ebbf9bd6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether b8:27:eb:bf:9b:d6 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether b8:27:eb:ea:ce:83 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.92/24 brd 192.168.178.255 scope global wlan0
valid_lft forever preferred_lft forever
inet6 fe80::5cc8:f41e:77d9:40f3/64 scope link
valid_lft forever preferred_lft forever
default via 192.168.178.1 dev wlan0 src 192.168.178.92 metric 303
192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.92 metric 303
Yes, that always helps. The problem is that at the moment it doesn't work reliably.
No, I didn't change any configurations in between these posts. I guess the router shows up as name server, because when the problem occurs, the Pi is disconnected from the network and so the "linux-ehou" "falls back" to the router as a name server.
So far I didn't seem to have any issues with that, but thank you, I will adjust it. So far I had only set it up through Yast, so I wasn't entirely sure what's happening behind the scenes...