Please follow the below template, it will help us to help you!
If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.
Expected Behaviour:
[I have my ISP modem at 192.168.254.1 range - I am using an Asus router RT-AC68P (192.168.1.1) from LAN (ISP) to WAN (Asus) as the main. I have a dedicated computer on Ubuntu running Pi-hole on Asus network 192.168.1.175. It's working great, but devices connected to the ISP modem cannot use Pihole DNS. I thought maybe the easiest way is to connect the PC running Pi-hole to the ISP modem, then configure the Asus router to point devices to Pihole which would be on a different IP address (192.168.254.1 - - - is this possible? If not, what would be the best option for me?
I can get to the setup page of the ISP modem by typing 192.168.254.254 while connected to the Asus network 192.168.1.1]
Actual Behaviour:
[replace this text with what is actually happening]
Debug Token:
[Replace this text with the debug token provided from running pihole -d (or running the debug script through the web interface]
@Fotingo Based on your post, it appears that your ISP modem is combination modem & router, or gateway device, and not a simple modem. If this the case, then both it and your Asus router are both configred as routers and you have what is known as a "Double NAT" condition. Regarless, the issue you are seeing is related to this as devices connected to the gateway & those connected to the Asus are on separate IP subnets. There are two possible ways to get around this:
Reconfigure either the gateway or the Asus as a bridge.
Thanks Tesserax..
Because of my situation, setting up the ISP modem to bridge mode is not an option.
What about if I add another router and set it under a different subnet.. how can I point all devices connected to to that router to use pihole dns?
What I am looking for is.. I have 5 wireless security cameras and I would like to completely separate them from my main network. I use an Asus RT-AC68 router that has Guest network option, but that's through vlans.. I prefer for that connection to be completely off the network.
So my main network is 192.168.1.1. I have pihole setup on another computer running in Docker
on IP 192.168.1.32.
I would like to setup another wireless router on let's say 192.168.250.1 network and have all the cameras connect to it.
How can I point that new network to use pihole?
EDIT:
The main reason behind this is because when all the cameras are connected to the main router, it bogs down the internet and I get ping of 100-200+... even with Qos setup or not.
So, I noticed that if the cameras are connected to another router with DHCP, the ping is normal and no issues with internet speeds...so I thought it's due to the Asus router not being able to handle too many devices?
I have confirmed this several times.. whenever the cameras are on the Asus, issue starts immediately... once I remove them, issue is gone.
I believe what you are looking for could be accomplished with network hardware that supports VLANs on both the routers and the Ethernet switches. In my case, I have a network comprised of Ubiquiti UniFi hardware. I have created multiple VLANs for things like game platforms, media devices, IoT, guests, etc. I employ a pair of Pi-holes (both hosted on separate Raspberry Pi 3B+s. The Pi's are located on my Management VLAN, and I use firewall rules to allow other VLANs to access them as needed.
Sorry, but I can't provide you with a step-by-step as I don't have your equipment to try it out on. In my case, my USG security gateway (aka, router) handles traffic between VLANs and has been configured with firewall rules to allow clients on selected VLANs to make DNS requests to the Pi-holes. I also employ UniFi managed Ethernet switches which are required to properly configure their individual ports to know where to send tagged VLAN traffic on. I don't know how you would do the same with your hardware.