My router is at 192.168.0.1 on my network. By accessing that address in my browser I should be able to reach the router admin page. My pihole is running in a docker container on raspbian bullseye and is configured to be the DHCP server with the router at 192.168.0.1
Actual Behaviour:
Once I started using pihole, I stopped being able to reach the router admin page. The router still manages all the traffic from the network and the pihole is properly blocking about 20% on requests. I can ping the router ip from my desktop. I simply cannot reach the web interface on the router by typing in the address anymore. IF I reboot the router, I will be able to reach the admin page for somewhere between 5 and 10 minutes, before all requests start timing out.
Thanks for the responses. The exact address is http://192.168.0.1/start.htm. And that works fine just after a fresh reboot of the router for about 10 minutes (like right now). http://192.168.0.1/ also works fine just after reboot, but not after 10 minutes or so (timeframe is not exact -- haven't actually timed it)
yes. That and http://192.168.0.1/start.html (which is the usual address) Both work normally or after a fresh reboot of the router for 10 or so minutes (rebooting the pihole doesn't help)