I switched from a Virgin Hub 3 to a Technicolor DGA0122. To enable my Pi-hole configuration to work with the Technicolor router, I changed the following in the default router configuration:
-
Changed the gateway address to 192.168.0.1 (to be the same as my Virgin router)
-
Switched off DCHP (as I used the DCHP in Pi-hole with my Virgin router, and wish to continue)
The basic functions of Pi-hole are working as far as I can tell, but there are a couple of small issues. They are not too troublesome in themselves, but I am concerned that they are indicative of a configuration error that may have other consequences.
Accessing web interface
I cannot access the web interface to Pi-hole using http://pi.hole/admin/index.php, which is the expected behaviour and what happened before I switched routers. But I can if I replace "pi.hole" by the IP address of my Pi-hole machine.
Re-enabling blocking
After disabling blocking through the web interface, "Enable Blocking" does not work immediately. That is the expected behaviour and what happened before I switched routers. I've tried flushing the DNS cache, and accessing different websites that should be blocked, and I can still see them. After a few minutes blocking resumes.
Pi-hole v5.17.1
FTL v5.23
Web Interface v5.20.1
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian