NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
How to disable DHCP on R7000P
I can uncheck the DHCP box on Advanced/Setup/LAN Setup but when I attempt to Apply the changed configuration, I get the error message "The IP address conflicts with the WAN IP subnet. Please enter a ...
Success!
I'm on the latest firmware: V1.3.1.64_10.1.36
I did a hard reset and reconfigured the router. On the page Advanced/Setup/LAN Setup, I changed the router IP to 192.168.10.1 and hit Apply. Once the router rebooted, I changed the IP back tp 192.168.1.1, turned off the DHCP Server and hit Apply. Also turned on the DHCP Server on the Pi-Hole. This got everything working. Apparently the router wants to see a change in it's IP address when turning off the DHCP Server. I don't know why.
Netgear does not really want to understand the need to run an internal (LAN side) DNS server - the Netgear consumer routers don't allow configuring LAN-side DNS servers e.g. a Pi-hole why ever. The issues here where the DHCP is forced enable looks like a bug to me. If the router would allow a proper DNS config, operating the DHCP on the router would not be the worst idea.
One issue more for ChristineT 's list of problems to report to the consumer BU management.
> [...] looks like a bug to me. [...]
I agree.
> [...] reinstalled the firmware [...]
You might try loading some different/older firmware but I wouldn't
expect much.
Thanks, I'll try older firmware. But I think you're probably right, it will likely not help.
Also, I said the DNS server was working fine on the Pi-Hole. Not quite true. Every request shows as coming from the router (192.168.1.1) which decreases the usefulness of the Query Log. DNS Requests should be forwarded by the router (pass through) rather than answered by proxy.
Badock wrote:Also, I said the DNS server was working fine on the Pi-Hole. Not quite true. Every request shows as coming from the router (192.168.1.1) which decreases the usefulness of the Query Log.
Be happy your router model does allow defining a DNS server on a LAN IP - not all do.
Badock wrote:DNS Requests should be forwarded by the router (pass through) rather than answered by proxy.
This must be related to the router based DHCP server: It does put the router LAN IP as a DNS server to the host config, regardless of the DNS server config. Another shortcoming of these consumer products
I installed firmware V1.3.0.20_10.1.1 just to see what it would do. My error message when turning off DHCPD changed from complaining about the WAN IP to complaining about the LAN IP, which seems somewhat more reasonable. Changing the router IP from 192.168.1.1 to 192.168.10.1 allowed the changed to be saved.
I suspect that the complaint about the WAN IP is just a typo in the firmware source. I'll try changing the router IP when I reload the V1.3.1.64_10.1.36 firmware in a few days, just to see if it works, though I still don't know why it forces a change to the IP.