No internet after power outage

Balujuhu · 18 April 2025 18:35

Hi,

I have a little problem. I installed the latest version of dietpi, nginx and openmediavault yesterday.

Totday I placed the RaspberryPi5 in an other room and since then it can’t connect to the internet.

ifconfig

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 4a:18:ec:aa:90:fe  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 5 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.65  netmask 255.255.255.0  broadcast 192.168.1.255
        ether 2c:cf:67:d4:3a:a0  txqueuelen 1000  (Ethernet)
        RX packets 2952  bytes 595099 (581.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 568  bytes 106477 (103.9 KiB)
        TX errors 0  dropped 2 overruns 0  carrier 0  collisions 0
        device interrupt 104  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 398  bytes 36196 (35.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 398  bytes 36196 (35.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
tippe oder füge den Code hier ein

ip addr show:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 2c:cf:67:d4:3a:a0 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.65/24 brd 192.168.1.255 scope global dynamic eth0
       valid_lft 863418sec preferred_lft 863418sec
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 4a:18:ec:aa:90:fe brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

ip route:

default via 192.168.1.1 dev eth0 
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.65

I hope someone can help

Joulinar · 18 April 2025 20:19

Are you able to ping the gateway/router?

Balujuhu · 18 April 2025 20:31

Yes

root@DietPi:~# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.23 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.493 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.491 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.458 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.479 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=0.478 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=0.463 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=0.442 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=0.455 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=0.453 ms

Joulinar · 18 April 2025 20:33

What about

ping 8.8.8.8

Balujuhu · 18 April 2025 20:34

working

root@DietPi:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=59 time=20.6 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=59 time=23.0 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=59 time=48.6 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=59 time=20.0 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=59 time=18.4 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=59 time=19.3 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=59 time=19.2 ms

Joulinar · 18 April 2025 20:34

You have internet access

And is this working

ping google.com

Balujuhu · 18 April 2025 20:36

root@DietPi:~# ping google.com

ping: google.com: Temporary failure in name resolution

Joulinar · 18 April 2025 20:37

There is an issue with your DNS configuration

Did you use a local DNS server like PiHole or AGH?

Balujuhu · 18 April 2025 20:37

Yes, I use Pihole with unbound

Joulinar · 18 April 2025 20:39

Is PiHole running on the very same system? Did you set PiHole as upstream DNS server for this device? Do you use static IP or DHCP?

Balujuhu · 18 April 2025 20:43

Pihole+unbound are running on a separate RaspberryPi.

I’m using DHCP in my router and the Raspberry has a static ip in the router.

I tried setting up my Pihole as DNS server and the router… both don’t work after power outage.

Joulinar · 18 April 2025 20:46

Did you check if you can see clients request from this device within PiHole log.

This I don’t understand fully. Maybe you can share the configuration

Balujuhu · 18 April 2025 20:54

In my router (192.168.1.1 fritzbox) Pihole (192.168.1.99) is set as DNS server. I tried in dietpi both ip addresses as dns server…

Joulinar · 18 April 2025 20:56

what about this

Balujuhu · 18 April 2025 21:00

Joulinar · 18 April 2025 21:06

did you find the test/log for the google domain we did?

Balujuhu · 18 April 2025 21:09

No.

In the config I can’t see the DNS server.

Joulinar · 18 April 2025 21:15

cat /etc/fstab

Balujuhu · 18 April 2025 21:17

# You can use "dietpi-drive_manager" to setup mounts.
# NB: It overwrites and re-creates physical drive mount entries on use.
#----------------------------------------------------------------
# NETWORK
#----------------------------------------------------------------
#----------------------------------------------------------------
# TMPFS
#----------------------------------------------------------------
tmpfs /tmp tmpfs size=4032M,noatime,lazytime,nodev,nosuid,mode=1777
tmpfs /var/log tmpfs size=50M,noatime,lazytime,nodev,nosuid
#----------------------------------------------------------------
# MISC: ecryptfs, vboxsf, glusterfs, mergerfs, bind, Btrfs subvolume
#----------------------------------------------------------------
#----------------------------------------------------------------
# SWAP SPACE
#----------------------------------------------------------------

#----------------------------------------------------------------
# PHYSICAL DRIVES
#----------------------------------------------------------------
PARTUUID=e7672f1c-02 / ext4 noatime,nodiratime,lazytime,rw 0 1
PARTUUID=e7672f1c-01 /boot/firmware vfat noatime,lazytime,rw 0 2

# >>> [openmediavault]
/dev/disk/by-uuid/08d97a03-d557-4d4d-8e13-5ec5f5fef18f /srv/dev-disk-by-uuid-08d97a03-d557-4d4d-8e13-5ec5f5fef18f ext4 defaults,nofail,user_xattr,usrquota,grpquota,acl 0 2
/dev/disk/by-uuid/88ae6eea-9a59-4ddc-b867-e73324b9ec8e /srv/dev-disk-by-uuid-88ae6eea-9a59-4ddc-b867-e73324b9ec8e ext4 defaults,nofail,user_xattr,usrquota,grpquota,acl 0 2
# <<< [openmediavault]

Joulinar · 18 April 2025 21:25

ah sorry wrong file, already tooo late today.

this one

cat /etc/resolv.conf