I would like help on setting one PiHole for the whole network → This means that the Wifi and Ethernet Network, Guest wifi and IoT wifi all use the PiHole.
That did NOT work, and would like some help to understand why.
Steps:
Connected Laptop to ISP Router by Cable
Connected PiHole to ISP Router by Cable
Connected Computer to Deco Mesh Router by Cable
Setup ISP Router to give static IP to PiHole
Setup new static IP to PiHole
Set the new PiHole IP Address as new DNS Server Address
In Main Deco
In Laptop
Restarted all machines
Verified DNS Address is received in DHCP
Expected:
Laptop network to work
Computer network to work
Actual:
DHCP sent the new PiHole Address
Laptop was able to connect fine since it was straight up on the ISP router along the PiHole
Computer was NOT able to connect → since it was in the Deco Network → Cant reach pihole ???
TL;DR → Can someone help me setting PiHole IP Address in a global way so the Deco devices can also reach it ? How to setup it on the ISP router and make it reachable to the Deco Routers as well ?
If you reach this far, thank you very much. Appreciate your time and help.
Thanks also to the team behind the project (big kudos to any contributors !)
I dont have a solution for you but, what allot of routers do is isolate clients in the guest network in a /31 subnet (2 addresses) with only the client and router IP.
So no way out to other IP's without additional routes or NATing.
Thanks for the info.
I am guessing that I will have to de-prioritize guest network from working with the PiHole.
At least, if they can connect to “an network” and use it, they will be fine. And since the Guest Network should be isolated, that is fine by me for now.
You are correct:
IF device is isolated
THEN it does not work
DUE to device not able to connect to the DNS PiHole.
For any device to work, it has to be NOT isolated.
The funny thing is: That is NOT an option for the TP-Link so called “IoT Network“ and “Guest Network“.
DUE to these Networks coping the DNS address from the Main Network configuration.
AND TP-Link always isolating them (non configurable).
If you know anything around those constraints let me know, but since they are “hardcoded“ on the Decos to act like that, it seems to have little hope changing that part.
“So no way out to other IP's without additional routes or NATing. “
I dont have experience with those, that is why I tried to set the addresses directly on the Main Deco to point the DNS to the Main ISP Router [1] that is then configured to have the DHCP to point to the PiHole[2]. (see picture above)
I checked both the Deco Router and the ISP Router → both have those options available to be configured.
Maybe I just need to learn more about those and try something out
Quick Question: Would using those configurations make it work ?
Example Configuration (static route idea)
Router
Setting
Value
ISP Router
Static Route
Destination: 192.168.2.0 (ISP Network to Deco Network as target )
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.2 (IP of Deco Router on ISP Router)
------
------
------
Deco Router
Static Route
Destination: 192.168.1.0 (Deco Network to ISP Network as target
Subnet Mask: 255.255.255.0
Gateway: 192.168.2.1 (IP of ISP Router on Deco Router)
DHCP DNS Server
192.168.1.10 (IP of PiHole on ISP Router)
Maybe firewalls could be what is messing things here (need to check)
In theory, that gist should work no ?
Altough not a priority, even if the device is isolated - on main, guest or IoT network - they will ask Deco Router for the PiHole address, and the Deco Router itself will know how to forward the requests.
Any info to quickstart or some guidelines\gist would be highly appreciated.
(need to check)