Timeout in local network using pi-hole

Help Community Help
1

The issue I am facing:
I use pi hole for quite some time now. Since a few weeks I repeatly have timeout problems reaching 1. pihole webinterface 2. pihole ssh 3. local router interface. Most of the times everything works, sometimes it does not. Most of the times its the pihole interface not working, sometimes its just the router interface, sometimes its both. Sometimes it works from my iPhone and not from my mac, sometimes it does not work at all. I tried different things, like reinstalling my raspberry with the newest raspbian and pi-hole. But I cannot find the problem. Sometimes I habe the feeling it might have something to do with my sonos system.

Debug token: https://tricorder.pi-hole.net/403Ks1KE/

2

Multicast DNS Storms are a real thing...

Since you seem to be German you might want to have a look in the German sub-forum here :wink:

3

Do I get more help there? :grin:

4

Is your pi-hole using WiFi? Intermittent timeouts can be caused by WiFi issues.

From your computer please send the output of

Windows OS: ping -t <pi-hole IP>

Linux OS: ping <pihole IP>

Let it run for 5 minutes or so, then press ctrl + C and send the % dropped/recieved.

5

No wifi. Pings go through.

6

We are going to need more information. What's your router? Do you have any network switches? Is your LAN segmented with VLANS? How many DHCP servers do you run? Intermittent connectivity issues do not usually occur with a simple LAN setup.

7

As a follow-up question, are you accessing these services through their DNS hostnames, or IP addresses?

8

Router: fritzbox 7690, there is one netgear switch (but problem occours also without switch). No vlans, one dhcp via fritzbox (ipv4/ipv6).
Accessing the interfaces via dns and ip (both do not work).

9

Does the issue still happen with IPv6 disabled in your router?

When the issue occurs, try running:

Windows: tracert <pi-hole IP>

Linux/MacOS: traceroute <pi-hole IP>

10

yea, I just had the same idea. It seems as if it does not. I now have dnsv6 activated but dhcpv6 deactivated. No more problems since then.

11

Okay, no, I still have the same problem.

traceroute to 192.168.188.70 (192.168.188.70), 64 hops max, 40 byte packets
 1  * * *
 2  pi.hole (192.168.188.70)  13.382 ms *  10.073 ms

PING 192.168.188.70 (192.168.188.70): 56 data bytes
64 bytes from 192.168.188.70: icmp_seq=0 ttl=64 time=9.436 ms
Request timeout for icmp_seq 1
 Request timeout for icmp_seq 2
64 bytes from 192.168.188.70: icmp_seq=3 ttl=64 time=11.279 ms
64 bytes from 192.168.188.70: icmp_seq=4 ttl=64 time=10.041 ms
64 bytes from 192.168.188.70: icmp_seq=5 ttl=64 time=11.280 ms
Request timeout for icmp_seq 6
64 bytes from 192.168.188.70: icmp_seq=7 ttl=64 time=6.096 ms
64 bytes from 192.168.188.70: icmp_seq=8 ttl=64 time=2.932 ms
64 bytes from 192.168.188.70: icmp_seq=9 ttl=64 time=9.666 ms
64 bytes from 192.168.188.70: icmp_seq=10 ttl=64 time=3.434 ms
64 bytes from 192.168.188.70: icmp_seq=11 ttl=64 time=9.659 ms
64 bytes from 192.168.188.70: icmp_seq=12 ttl=64 time=10.125 ms
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
64 bytes from 192.168.188.70: icmp_seq=15 ttl=64 time=9.904 ms
64 bytes from 192.168.188.70: icmp_seq=16 ttl=64 time=9.908 ms
Request timeout for icmp_seq 17
64 bytes from 192.168.188.70: icmp_seq=18 ttl=64 time=3.099 ms
64 bytes from 192.168.188.70: icmp_seq=19 ttl=64 time=3.029 ms
64 bytes from 192.168.188.70: icmp_seq=20 ttl=64 time=7.191 ms
^C
--- 192.168.188.70 ping statistics ---
21 packets transmitted, 15 packets received, 28.6% packet loss
round-trip min/avg/max/stddev = 2.932/7.805/11.280/3.099 ms

In journalctl I have since 5.30 am:
(I changed the ipv6 of my pi hole to fd6a:3bac:mac-pi-hole in this text)

Mar 04 05:33:57 raspberrypi avahi-daemon[398]: Registering new address record for 2003:ed:5f4f:8000:c2ae:6258:fa1e:9a62 on eth0.*.
Mar 04 05:33:58 raspberrypi avahi-daemon[398]: Withdrawing address record for 2003:ed:5f4f:8000:c2ae:6258:fa1e:9a62 on eth0.
Mar 04 05:42:36 raspberrypi avahi-daemon[398]: Registering new address record for 2003:ed:5f4f:8000:c2ae:6258:fa1e:9a62 on eth0.*.
Mar 04 05:42:37 raspberrypi avahi-daemon[398]: Withdrawing address record for 2003:ed:5f4f:8000:c2ae:6258:fa1e:9a62 on eth0.
Mar 04 06:17:01 raspberrypi CRON[54196]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 04 06:17:01 raspberrypi CRON[54197]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Mar 04 06:17:01 raspberrypi CRON[54196]: pam_unix(cron:session): session closed for user root
Mar 04 06:25:01 raspberrypi CRON[54241]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 04 06:25:01 raspberrypi CRON[54242]: (root) CMD (test -x /usr/sbin/anacron || { cd / && run-parts --report /etc/cron.daily; })
Mar 04 06:25:01 raspberrypi CRON[54241]: pam_unix(cron:session): session closed for user root
Mar 04 06:35:22 raspberrypi systemd[1]: Starting apt-daily-upgrade.service - Daily apt upgrade and clean activities...
Mar 04 06:35:24 raspberrypi systemd[1]: apt-daily-upgrade.service: Deactivated successfully.
Mar 04 06:35:24 raspberrypi systemd[1]: Finished apt-daily-upgrade.service - Daily apt upgrade and clean activities.
Mar 04 06:35:24 raspberrypi systemd[1]: apt-daily-upgrade.service: Consumed 1.312s CPU time.
Mar 04 07:17:01 raspberrypi CRON[54532]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 04 07:17:01 raspberrypi CRON[54533]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Mar 04 07:17:01 raspberrypi CRON[54532]: pam_unix(cron:session): session closed for user root
Mar 04 08:17:01 raspberrypi CRON[54810]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 04 08:17:01 raspberrypi CRON[54811]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Mar 04 08:17:01 raspberrypi CRON[54810]: pam_unix(cron:session): session closed for user root
Mar 04 08:21:38 raspberrypi sshd[54832]: Connection closed by 192.168.188.126 port 59864 [preauth]
Mar 04 08:27:59 raspberrypi avahi-daemon[398]: Withdrawing address record for fd6a:3bac:mac-pi-holeon eth0.
Mar 04 08:27:59 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
Mar 04 08:27:59 raspberrypi avahi-daemon[398]: Registering new address record for fe80::6d0c:b60e:b136:aac8 on eth0.*.
Mar 04 08:28:12 raspberrypi avahi-daemon[398]: Withdrawing address record for fd6a:3bac:mac-pi-holeon eth0.
Mar 04 08:28:12 raspberrypi avahi-daemon[398]: Withdrawing address record for fe80::6d0c:b60e:b136:aac8 on eth0.
Mar 04 08:28:12 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
Mar 04 08:28:13 raspberrypi avahi-daemon[398]: Withdrawing address record for fd6a:3bac:mac-pi-holeon eth0.
Mar 04 08:28:13 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
Mar 04 08:28:13 raspberrypi avahi-daemon[398]: Registering new address record for fe80::6d0c:b60e:b136:aac8 on eth0.*.
Mar 04 08:28:17 raspberrypi avahi-daemon[398]: Withdrawing address record for fd6a:3bac:mac-pi-holeon eth0.
Mar 04 08:28:17 raspberrypi avahi-daemon[398]: Withdrawing address record for fe80::6d0c:b60e:b136:aac8 on eth0.
Mar 04 08:28:17 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
Mar 04 08:28:18 raspberrypi avahi-daemon[398]: Withdrawing address record for fd6a:3bac:mac-pi-holeon eth0.
Mar 04 08:28:18 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
Mar 04 08:28:18 raspberrypi avahi-daemon[398]: Registering new address record for fe80::6d0c:b60e:b136:aac8 on eth0.*.
Mar 04 08:28:21 raspberrypi avahi-daemon[398]: Withdrawing address record for fd6a:3bac:mac-pi-holeon eth0.
Mar 04 08:28:21 raspberrypi avahi-daemon[398]: Withdrawing address record for fe80::6d0c:b60e:b136:aac8 on eth0.
Mar 04 08:28:21 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
Mar 04 08:28:23 raspberrypi avahi-daemon[398]: Withdrawing address record for fd6a:3bac:mac-pi-holeon eth0.
Mar 04 08:28:23 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
Mar 04 08:28:23 raspberrypi avahi-daemon[398]: Registering new address record for fe80::6d0c:b60e:b136:aac8 on eth0.*.
Mar 04 08:30:01 raspberrypi avahi-daemon[398]: Withdrawing address record for fd6a:3bac:mac-pi-holeon eth0.
Mar 04 08:30:01 raspberrypi avahi-daemon[398]: Withdrawing address record for fe80::6d0c:b60e:b136:aac8 on eth0.
Mar 04 08:30:01 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
Mar 04 08:30:03 raspberrypi avahi-daemon[398]: Withdrawing address record for fd6a:3bac:mac-pi-holeon eth0.
Mar 04 08:30:03 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
Mar 04 08:30:03 raspberrypi avahi-daemon[398]: Registering new address record for fe80::6d0c:b60e:b136:aac8 on eth0.*.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for fd6a:3bac:mac-pi-holeon eth0.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for 2003:ed:5f17:d800:eff7:ba73:639:2239 on eth0.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for fe80::6d0c:b60e:b136:aac8 on eth0.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for ::1 on lo.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for 127.0.0.1 on lo.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Host name conflict, retrying with raspberrypi-2
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for 2003:ed:5f17:d800:eff7:ba73:639:2239 on eth0.*.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for fe80::6d0c:b60e:b136:aac8 on eth0.*.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for 192.168.188.70 on eth0.IPv4.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for ::1 on lo.*.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for 127.0.0.1 on lo.IPv4.
Mar 04 08:30:04 raspberrypi NetworkManager[476]: <info>  [1741073404.6244] policy: set 'Wired connection 1' (eth0) as default for IPv6 routing a>
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for fd6a:3bac:mac-pi-holeon eth0.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for fe80::6d0c:b60e:b136:aac8 on eth0.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for 2003:ed:5f17:d800:eff7:ba73:639:2239 on eth0.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for 192.168.188.70 on eth0.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for ::1 on lo.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for 127.0.0.1 on lo.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Host name conflict, retrying with raspberrypi-3
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for 2003:ed:5f17:d800:eff7:ba73:639:2239 on eth0.*.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for 192.168.188.70 on eth0.IPv4.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for ::1 on lo.*.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for 127.0.0.1 on lo.IPv4.
Mar 04 08:30:07 raspberrypi avahi-daemon[398]: Server startup complete. Host name is raspberrypi-3.local. Local service cookie is 1763300331.
Mar 04 08:31:09 raspberrypi avahi-daemon[398]: Withdrawing address record for fd6a:3bac:mac-pi-holeon eth0.
Mar 04 08:31:09 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for 127.0.0.1 on lo.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for 127.0.0.1 on lo.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for 127.0.0.1 on lo.
Mar 04 08:30:01 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
Mar 04 08:30:03 raspberrypi avahi-daemon[398]: Withdrawing address record for fd6a:3bac:mac-pi-holeon eth0.
Mar 04 08:30:03 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
Mar 04 08:30:03 raspberrypi avahi-daemon[398]: Registering new address record for fe80::6d0c:b60e:b136:aac8 on eth0.*.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for fd6a:3bac:mac-pi-holeon eth0.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for 2003:ed:5f17:d800:eff7:ba73:639:2239 on eth0.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for fe80::6d0c:b60e:b136:aac8 on eth0.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for ::1 on lo.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for 127.0.0.1 on lo.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Host name conflict, retrying with raspberrypi-2
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for 2003:ed:5f17:d800:eff7:ba73:639:2239 on eth0.*.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for fe80::6d0c:b60e:b136:aac8 on eth0.*.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for 192.168.188.70 on eth0.IPv4.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for ::1 on lo.*.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for 127.0.0.1 on lo.IPv4.
Mar 04 08:30:04 raspberrypi NetworkManager[476]: <info>  [1741073404.6244] policy: set 'Wired connection 1' (eth0) as default for IPv6 routing a>
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for fd6a:3bac:mac-pi-holeon eth0.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for fe80::6d0c:b60e:b136:aac8 on eth0.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for 2003:ed:5f17:d800:eff7:ba73:639:2239 on eth0.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for 192.168.188.70 on eth0.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for ::1 on lo.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Withdrawing address record for 127.0.0.1 on lo.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: **Host name conflict, retrying with raspberrypi-3**
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for 2003:ed:5f17:d800:eff7:ba73:639:2239 on eth0.*.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for 192.168.188.70 on eth0.IPv4.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for ::1 on lo.*.
Mar 04 08:30:04 raspberrypi avahi-daemon[398]: Registering new address record for 127.0.0.1 on lo.IPv4.
Mar 04 08:30:07 raspberrypi avahi-daemon[398]: Server startup complete. Host name is raspberrypi-3.local. Local service cookie is 1763300331.
Mar 04 08:31:09 raspberrypi avahi-daemon[398]: Withdrawing address record for fd6a:3bac:mac-pi-holeon eth0.
Mar 04 08:31:09 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
Mar 04 08:31:09 raspberrypi avahi-daemon[398]: Registering new address record for fe80::6d0c:b60e:b136:aac8 on eth0.*.
Mar 04 08:32:08 raspberrypi avahi-daemon[398]: Withdrawing address record for fd6a:3bac:mac-pi-holeon eth0.
Mar 04 08:32:08 raspberrypi avahi-daemon[398]: Withdrawing address record for fe80::6d0c:b60e:b136:aac8 on eth0.
Mar 04 08:32:08 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
Mar 04 08:32:09 raspberrypi avahi-daemon[398]: Withdrawing address record for fd6a:3bac:mac-pi-holeon eth0.
Mar 04 08:32:09 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
Mar 04 08:32:09 raspberrypi avahi-daemon[398]: Registering new address record for fe80::6d0c:b60e:b136:aac8 on eth0.*.
Mar 04 08:32:11 raspberrypi NetworkManager[476]: <info> [1741073531.5668] policy: set 'Wired connection 1' (eth0) as default for IPv6 routing a>
Mar 04 08:32:11 raspberrypi avahi-daemon[398]: Withdrawing address record for fd6a:3bac:mac-pi-holeon eth0.
Mar 04 08:32:11 raspberrypi avahi-daemon[398]: Withdrawing address record for fe80::6d0c:b60e:b136:aac8 on eth0.
Mar 04 08:32:11 raspberrypi avahi-daemon[398]: Registering new address record for fd6a:3bac:mac-pi-holeon eth0.*.
12

It looks like your pi-hole is dropping it's IP intermittently. Does it have a static IP address?

13

This looks like a network issue. In your above comments you say no wifi but those pings have a lot of latency for ethernet ( assuming a home network ) and 26% packet loss is a lot. Perhaps you have a bad ethernet cable somewhere.

14

It does. But maybe that is my fault, because I was changing ipv6 dhcp announcement to try if I get access to pi hole.

15

I do have wifi, but my pihole just uses thernet to the router. In my experience this keeps happening the longer the raspberry is up. I just tried clonung and uaing another sd card to rule more causes out.

16

Because this is still happening even after a reinstall of the pi, there are really two possible conclusions:

  1. As @CallMeCurious stated, you have a bad ethernet cable. It's advised to try some new ones.

  2. Something is wrong within your router itself. You can verify this by plugging the ethernet cable from the pi directly into your computer and setting a static ip on your computer to the same subnet. Then start to ping the pi-hole. If there are no drops with the same cable you are using to connect the pi to the router, the issue is your router.

You may also try to use wireshark and see what is happening at the packet level. It may provide some extra insight.

17

I mean it could only be the ethernet cable between pi and my router right? I already thought of that and changed it without success.

I was running the debug function in my raspberry after noticing rare ntp connection errors or errors that on ipv6 upstream dns is not reachable. It seems, that from time to time there are connection problems. I can see in my router settings, that at this time there is not anymore wifi traffic.

   2025-03-06 00:00:04.124 CET [588/T10158] ERROR: Cannot receive UDP DNS reply: Timeout - no response from upstream DNS server
   2025-03-06 00:00:04.124 CET [588/T10158] INFO: Tried to resolve PTR "47.188.168.192.in-addr.arpa" on 127.0.0.1#53 (UDP)
   2025-03-06 00:06:18.620 CET [588/T10155] ERROR: Failed to receive data from NTP server ptbtime1.ptb.de (2001:638:610:be01::108): Timeout
   2025-03-06 00:06:23.740 CET [588/T10155] ERROR: Failed to receive data from NTP server ptbtime1.ptb.de (2001:638:610:be01::108): Timeout
   2025-03-06 00:06:28.860 CET [588/T10155] ERROR: Failed to receive data from NTP server ptbtime1.ptb.de (2001:638:610:be01::108): Timeout
   2025-03-06 00:06:33.980 CET [588/T10155] ERROR: Failed to receive data from NTP server ptbtime1.ptb.de (2001:638:610:be01::108): Timeout
   2025-03-06 00:06:39.612 CET [588/T10155] ERROR: Failed to receive data from NTP server ptbtime1.ptb.de (2001:638:610:be01::108): Timeout
   2025-03-06 00:06:44.732 CET [588/T10155] ERROR: Failed to receive data from NTP server ptbtime1.ptb.de (2001:638:610:be01::108): Timeout
   2025-03-06 00:06:49.852 CET [588/T10155] ERROR: Failed to receive data from NTP server ptbtime1.ptb.de (2001:638:610:be01::108): Timeout
   2025-03-06 00:06:49.852 CET [588/T10155] INFO: Received 1/8 valid NTP replies from ptbtime1.ptb.de
   2025-03-06 00:06:49.852 CET [588/T10155] INFO: Time offset: 1.282692e-01 ms (excluded 7 outliers)
   2025-03-06 00:06:49.852 CET [588/T10155] INFO: Round-trip delay: 2.069187e+01 ms (excluded 7 outliers)
   2025-03-06 01:06:18.024 CET [588/T10155] INFO: Received 8/8 valid NTP replies from ptbtime1.ptb.de
   2025-03-06 01:06:18.024 CET [588/T10155] INFO: Time offset: 3.000668e-01 ms (excluded 1 outliers)
   2025-03-06 01:06:18.025 CET [588/T10155] INFO: Round-trip delay: 2.043056e+01 ms (excluded 1 outliers)
   2025-03-06 01:11:06.151 CET [588/T10156] INFO: Optimized database in 0.132 seconds
   2025-03-06 02:06:18.271 CET [588/T10155] INFO: Received 8/8 valid NTP replies from ptbtime1.ptb.de
   2025-03-06 02:06:18.271 CET [588/T10155] INFO: Time offset: 6.429255e-01 ms (excluded 0 outliers)
   2025-03-06 02:06:18.272 CET [588/T10155] INFO: Round-trip delay: 2.023989e+01 ms (excluded 0 outliers)
   2025-03-06 03:06:18.450 CET [588/T10155] INFO: Received 8/8 valid NTP replies from ptbtime1.ptb.de
   2025-03-06 03:06:18.450 CET [588/T10155] INFO: Time offset: 2.208778e-01 ms (excluded 1 outliers)
   2025-03-06 03:06:18.450 CET [588/T10155] INFO: Round-trip delay: 2.037586e+01 ms (excluded 1 outliers)
   2025-03-06 04:06:19.644 CET [588/T10155] ERROR: Failed to receive data from NTP server ptbtime1.ptb.de (2001:638:610:be01::108): Timeout
   2025-03-06 04:06:25.276 CET [588/T10155] ERROR: Failed to receive data from NTP server ptbtime1.ptb.de (2001:638:610:be01::108): Timeout
   2025-03-06 04:06:30.396 CET [588/T10155] ERROR: Failed to receive data from NTP server ptbtime1.ptb.de (2001:638:610:be01::108): Timeout
   2025-03-06 04:06:36.028 CET [588/T10155] ERROR: Failed to receive data from NTP server ptbtime1.ptb.de (2001:638:610:be01::108): Timeout
   2025-03-06 04:06:41.148 CET [588/T10155] ERROR: Failed to receive data from NTP server ptbtime1.ptb.de (2001:638:610:be01::108): Timeout
   2025-03-06 04:06:41.669 CET [588/T10155] INFO: Received 3/8 valid NTP replies from ptbtime1.ptb.de
   2025-03-06 04:06:41.669 CET [588/T10155] INFO: Time offset: 6.022453e-01 ms (excluded 5 outliers)
   2025-03-06 04:06:41.669 CET [588/T10155] INFO: Round-trip delay: 2.054246e+01 ms (excluded 5 outliers)
   2025-03-06 05:06:18.914 CET [588/T10155] INFO: Received 8/8 valid NTP replies from ptbtime1.ptb.de
   2025-03-06 05:06:18.914 CET [588/T10155] INFO: Time offset: -1.705374e+00 ms (excluded 1 outliers)
   2025-03-06 05:06:18.914 CET [588/T10155] INFO: Round-trip delay: 2.018847e+01 ms (excluded 1 outliers)
   2025-03-06 06:06:19.137 CET [588/T10155] INFO: Received 8/8 valid NTP replies from ptbtime1.ptb.de
   2025-03-06 06:06:19.137 CET [588/T10155] INFO: Time offset: -4.142932e+00 ms (excluded 1 outliers)

   -----tail of FTL.log------
   2025-03-06 13:02:28.092 CET [13811/T13876] ERROR: Failed to receive data from NTP server ptbtime1.ptb.de (2001:638:610:be01::108): Timeout
   2025-03-06 13:02:33.212 CET [13811/T13876] ERROR: Failed to receive data from NTP server ptbtime1.ptb.de (2001:638:610:be01::108): Timeout
   2025-03-06 13:02:38.332 CET [13811/T13876] ERROR: Failed to receive data from NTP server ptbtime1.ptb.de (2001:638:610:be01::108): Timeout
   2025-03-06 13:02:43.452 CET [13811/T13876] ERROR: Failed to receive data from NTP server ptbtime1.ptb.de (2001:638:610:be01::108): Timeout
   2025-03-06 13:02:48.572 CET [13811/T13876] ERROR: Failed to receive data from NTP server ptbtime1.ptb.de (2001:638:610:be01::108): Timeout
   2025-03-06 13:02:53.692 CET [13811/T13876] ERROR: Failed to receive data from NTP server ptbtime1.ptb.de (2001:638:610:be01::108): Timeout
   2025-03-06 13:02:58.812 CET [13811/T13876] ERROR: Failed to receive data from NTP server ptbtime1.ptb.de (2001:638:610:be01::108): Timeout
   2025-03-06 13:02:58.812 CET [13811/T13876] WARNING: Warning NTP client: No valid NTP replies received, check server and network connectivity
   2025-03-06 14:02:22.077 CET [13811/T13876] INFO: Received 8/8 valid NTP replies from ptbtime1.ptb.de
   2025-03-06 14:02:22.077 CET [13811/T13876] INFO: Time offset: -1.516253e+00 ms (excluded 0 outliers)
   2025-03-06 14:02:22.077 CET [13811/T13876] INFO: Round-trip delay: 2.026910e+01 ms (excluded 0 outliers)
   2025-03-06 15:02:22.341 CET [13811/T13876] INFO: Received 8/8 valid NTP replies from ptbtime1.ptb.de
   2025-03-06 15:02:22.341 CET [13811/T13876] INFO: Time offset: 5.359990e-01 ms (excluded 1 outliers)
   2025-03-06 15:02:22.341 CET [13811/T13876] INFO: Round-trip delay: 2.030734e+01 ms (excluded 1 outliers)
   2025-03-06 16:02:22.610 CET [13811/T13876] INFO: Received 8/8 valid NTP replies from ptbtime1.ptb.de
   2025-03-06 16:02:22.611 CET [13811/T13876] INFO: Time offset: 8.505583e-01 ms (excluded 0 outliers)
   2025-03-06 16:02:22.611 CET [13811/T13876] INFO: Round-trip delay: 2.029085e+01 ms (excluded 0 outliers)
   2025-03-06 17:02:22.871 CET [13811/T13876] INFO: Received 8/8 valid NTP replies from ptbtime1.ptb.de
   2025-03-06 17:02:22.871 CET [13811/T13876] INFO: Time offset: 5.823544e-01 ms (excluded 1 outliers)
   2025-03-06 17:02:22.872 CET [13811/T13876] INFO: Round-trip delay: 2.027144e+01 ms (excluded 1 outliers)
   2025-03-06 18:02:23.047 CET [13811/T13876] INFO: Received 8/8 valid NTP replies from ptbtime1.ptb.de
   2025-03-06 18:02:23.047 CET [13811/T13876] INFO: Time offset: 7.197261e-02 ms (excluded 0 outliers)
   2025-03-06 18:02:23.047 CET [13811/T13876] INFO: Round-trip delay: 2.022523e+01 ms (excluded 0 outliers)
   2025-03-06 19:02:23.315 CET [13811/T13876] INFO: Received 8/8 valid NTP replies from ptbtime1.ptb.de
   2025-03-06 19:02:23.315 CET [13811/T13876] INFO: Time offset: 6.515639e-01 ms (excluded 1 outliers)
   2025-03-06 19:02:23.315 CET [13811/T13876] INFO: Round-trip delay: 2.014937e+01 ms (excluded 1 outliers)
   2025-03-06 20:02:23.570 CET [13811/T13876] INFO: Received 8/8 valid NTP replies from ptbtime1.ptb.de
   2025-03-06 20:02:23.571 CET [13811/T13876] INFO: Time offset: 7.031986e-01 ms (excluded 1 outliers)
   2025-03-06 20:02:23.571 CET [13811/T13876] INFO: Round-trip delay: 2.018329e+01 ms (excluded 1 outliers)
18

You might want to install iperf3 on the pi / clients and run some tests to it. Not sure what your pi is but a basic test will give you some indication if your getting the proper bandwidth on the link and a more indepth test can give you some info on dropped packets.

IE on the pi run iperf3 -s ( make sure port 5201 is unblocked ) and on the client run iperf3 -s <pi's IP>
For a more indepth test run iperf3 -c <pi's IP> -u -t 30 -b 1M -l 1000 -P 3

19

Thanks, I am going to try that. Cannot do that right now, because I just moved.

I noticed something: Is it normal to have localhost and pi-hole under top clients? And there is another one I cannot rule out (may be my isp). As far as I understood pi-hole should not be part of client list.

Bildschirmfoto 2025-03-21 um 17.56.46
Bildschirmfoto 2025-03-21 um 17.56.461012×244 12.8 KB