NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Topology
Apr 27, 2020Virtuoso
RAX120 Firmware 1.0.1.122 (27 APR 2020)
NETGEAR has released new firmware for the RAX120 (see here): New Features and Enhancements * Supports NETGEAR Armor * Improves the device type and model detection Bug Fixes * Clients were una...
bamcgregor89
May 09, 2020Aspirant
I just don't even know how to deal with Netgear firmware updates anymore.
First, some background. After the DNS mess with 114 and 118, I had moved both DNS and DHCP to a Pi-Hole on my network because the router wasn't even forwarding DNS at all so I needed a DHCP server giving clients a DNS server that actually works.
Enter this firmware. Immediately after my router comes back up, my devices are all complaining that there's no internet. Okay. Ping to gateway - check. Ping to 8.8.8.8 - check. Routing is fine. DNS lookup? Failing. I can't ping my Pi-Hole anymore. Weird. I spend the next hour looking over the Pi-Hole - Static IP, subnet, gateway, DNS - all good - all exactly as it was before. It's 1:30am, I'm tired let's just set the router and see if it can handle DHCP and DNS for the night. As soon as the router has DHCP enabled again, suddenly I can ping and connect to my Pi-Hole via it's IP address. What? Turn DHCP on the router off, Pi-Hole goes away again. I can connect to every other device on my network but that Pi-Hole. It even shows in the router's Attached Devices list. Why does all traffic to it get blocked when DHCP is turned off on the router?
bamcgregor89
May 09, 2020Aspirant
I worked around my issue by killing DHCPCD in Linux.