Pihole -d fails gateway ping test, yet I can ping gateway no problem

Running pihole on Ubuntu 20.04 (x86)
Pi-hole v5.10
FTL v5.15
Web Interface v5.12

~$ 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=0.439 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.521 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.663 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.677 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.543 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=0.677 ms
^C
--- 192.168.1.1 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5100ms
rtt min/avg/max/mdev = 0.439/0.586/0.677/0.091 ms

Yet during pihole -d it fails

[i] Default IPv4 gateway: 192.168.1.1
192.168.1.1
   * Pinging 192.168.1.1
192.168.1.1...
ping: 192.168.1.1
192.168.1.1: Name or service not known
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)

in a later DHCP test it has no issues:

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
   Scanning all your interfaces for DHCP servers
   Timeout: 10 seconds

   * Received 300 bytes from eno1:192.168.1.1
     Offered IP address: 192.168.1.79
     Server IP address: 192.168.1.1
     Relay-agent IP address: N/A
     BOOTP server: (empty)
     BOOTP file: (empty)
     DHCP options:
      Message type: DHCPOFFER (2)
      server-identifier: 192.168.1.1
      lease-time: 86400 ( 1d )
      renewal-time: 43200 ( 12h )
      rebinding-time: 75600 ( 21h )
      netmask: 255.255.255.0
      broadcast: 192.168.1.255
      wpad-server: "
"
      router: 192.168.1.1
      dns-server: 192.168.1.79
      --- end of options ---

   DHCP packets received on interface eno1: 1
   DHCP packets received on interface lo: 0

Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

pihole -d

or do it through the Web interface:

Tools > Generate Debug Log

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.