The user interface for my THG3000 is shockingly bad. It's very slow to connect and register clicks and keeps randomly refreshing the page when I'm halfway through changing a setting. It very often times out when I'm trying to make any changes. Is this normal for this router?
I believe double NAT would entail the use of either a STUN server along with port forwarding, or an external resolver. I think STUN would be the easiest if it works, I can't test as I've done away with it altogether.
Can I check - the Synology running the Pi-hole is assigned a static IP address of 192.168.2.15 from the router. I was planning on deleting all DCHP reservations on the router and going into the Synology's settings to give it the same static IP address. I was hoping to keep the Synology's IP address the same as I have lots of things pointed at it. Would it work if I gave the DHCP range for the Pi-hole as 192.168.0.2 - 192.168.0.254 which obviously includes the Synology's address?
@dwl99 Assuming you want the NAS to always reside on 151, then on PiHole in DHCP settings under "Static DHCP leases configuration" you can supply MAC, IP address and hostname.
I turned off DHCP on the router and turned on DHCP in the pihole settings with the range 192.168.0.2 - 192.168.0.254, the NAS has a static address of 192.168.0.151 in its settings but I'm getting a pihole error message when I save the settings "There was a problem applying your settings. Debugging information: PHP error (2): fsockopen(): unable to connect to 127.0.0.1:4711 (Connection refused) in /var/www/html/admin/scripts/pi-hole/php/FTL.php:47"
