Pihole Blocking Wired but not wireless network

[DL6ER]

@starsick

On wireless, I am seeing no requests being made at all

Reading your post, this is no surprise at all, I'd say. The reason is that you separate your networks and I'd bet there is no routing information that would allow the wireless devices to find any wired devices.

Let me summarize your network and then tell me if I'm right with my assumption:

• Wired network: 192.168.111.*/24 (/24 translates into subnet mask 255.255.255.0)
• Wireless network: 192.168.0.*/24 (same subnet mask)

If this is the case and there is no advanced routing configured, the devices on the one network will not be able to see the devices on the other network. If the necessary routing information is there, it should work fine in terms of routing but there might still be a firewall in the wireless AP that prevents what you want from happening.

So let's investigate this together. The first think I'd like you to test if you can:

1. Ping the Pi-hole (192.168.111.6) from any wireless client
2. Ping the wireless client you used above from the Pi-hole

Both ways are necessary for the devices to be able to talk to the Pi-hole.

@starsick

Google 8.8.8.8 on both as secondary

Don't be fooled by the terms "primary" and "secondary"! This will only make your life harder, because you don't know why certain things are happening. I suggest you read an earlier post of mine about this topic:

Primary vs. Secondary DNS

Following the regulations, there is nothing like a primary and secondary DNS server. These indications are quite misleading but many systems adopted it this way. We only list the DNS servers as primary and secondary, because this is what the providers write on their pages. The bad phrasing is supported especially by how Windows handles it. If you look at any Linux distribution, there is usually no separation between primary and secondary, but you can only provide a comma-separated list of DNS se…