From 35% to 7% blocked after last updates

[jfb]

@DreadPirateWoberts

only client showing connected is the Orbi itself

The router is not advertising Pi-hole as DNS server, it is advertising its own IP:

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
   Scanning all your interfaces for DHCP servers
   Timeout: 10 seconds
   
   * Received 548 bytes from wlan0:10.0.0.1
     Offered IP address: 10.0.0.33
     Server IP address: N/A
     Relay-agent IP address: N/A
     BOOTP server: (empty)
     BOOTP file: (empty)
     DHCP options:
      Message type: DHCPOFFER (2)
      server-identifier: 10.0.0.1
      lease-time: 80103 ( 22h 15m 3s )
      netmask: 255.255.255.0
      router: 10.0.0.1
      dns-server: 10.0.0.1
      --- end of options ---
    
   DHCP packets received on interface wlan0: 1
   DHCP packets received on interface eth0: 0
   DHCP packets received on interface lo: 0

Why do I only see my router's IP address instead of individual devices in the Top Clients section and Query Log?

A nice feature of Pi-hole is that you can see which network devices are sending out the most DNS queries. For every device that is using Pi-hole as their DNS server, you can also see which DNS queries each one has made. [image] But depending on a few things, you may only see a single host in your Top Clients section, which is not as useful. [image] This isn't detrimental to the performance of your Pi-hole; it just provides you with less insight into what's happening on your network. So w…

@DreadPirateWoberts

Minimal ad blocking

You have multiple IP's assigned to the Pi, on different ranges:

** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] nutritioncigarheading.com is 0.0.0.0 on lo (127.0.0.1)
[✓] nutritioncigarheading.com is 0.0.0.0 on eth0 (192.168.1.166)
[✓] nutritioncigarheading.com is 0.0.0.0 on wlan0 (10.0.0.33)
[✓] doubleclick.com is 142.250.65.174 via a remote, public DNS server (8.8.8.8)

The active interface appears to be wlan0, but Pi-hole is configured for the eth0 interface:

** [ DIAGNOSING ]: Setup variables
 
    IPV4_ADDRESS=192.168.1.166/24

    PIHOLE_INTERFACE=eth0

Run pihole -r and select reconfigure to set up Pi-hole for the active IP and interface.