I am running v6 on RPI 5 with aarch64 Pi OS Bookworm.
I have interfaces wlan1, lo, wlan0,eth0 and tailscale0 connected, yet only requests from lo and wlan0 are answered. During initial v5 setup I selected wlan0 as my interface.
Now i have Interface Settings set to: Permit all origins
It also appears strange to me that after Bind only to interface no interface is listed.
In Settings<General the primary ip is coming from eth0.
Unfortunately, it's exactly this combination of things that is popping up with network issues all over the Internet. I have recently bought a RPI 5 myself in case we ever need to troubleshoot this and it seems there we are
Can you provide some hints how I being my own device into a configuration similar enough to yours?
This is causing your observation:
By way of your custom configuration, you are tying your Pi-hole to interface wlan0 exclusively, conflicting with Pi-hole's Permit all origins injecting except-interface=nonexistent.
If you remove interface=wlan0 and switch Pi-hole to its default Allow only local requests, your DNS service would be back online, covering all your host machine's network interfaces.
Your DHCP settings may yet need extra tweaking.
What's your intention here?
Serving DHCP only to clients connecting to an access point that you wish to run next to Pi-hole on the same machine?
Then you'd need some extra lines to remove DHCP services from your other interfaces, e.g.
no-dhcp-interface=tailscale0
Add one line to your /etc/dnsmasq.d/hostapd.conf for each interface that you do not want to offer DHCP services.
Check for potential syntax errors:
pihole-FTL dnsmasq-test
If OK, run pihole restartdns to take those settings into effect.
I recently reported the issue with not all interfaces being displayed in the web interface, i think you bought it then.
I will try to find out what i did exactly and try to reproduce this on a fresh install.
I can give more info about my system afterwards
instead of interface=wlan0 and now its working.
I just dont want the dhcp to intervene with my router on eth0, it is currently only in my home network for setup and playing around with.
I am still wondering why there is no interface displayed after Respond only on interface(image in original post)
I still need to set it to Permit all origins for request on my tailnet as otherwise i get the error that the device from the tailnet is a non-local device.
Warning in dnsmasq core:
ignoring query from non-local network 100.114.117.86 (logged only once)
Is this because of the 100.x range?
Im reading that 100.64.0.0–100.127.255.255 is for:
Shared address space for communications between a service provider and its subscribers when using a carrier-grade NAT.
No, this is a tailscale-specific issue that has been discussed elsewhere on this forum before: Local networks are those you have a matching local interface for, e.g., your eth0 is 192.168.178.158/24 so 192.168.178.1 - 192.168.178.255 is "local". The tailscale interface, however, is /32 network so NO other address is local to this interface.
I am considering buying a Raspberry Pi 5 because of specific MongoDB needs (ARMv8.2-A instruction set) and the same Pi will also host Pi-Hole v6 when the Stable version has been released in the future
