NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RAX120 Router Random Disconnects
Hey everyone, I know that I'm not the only one with problems on the Nighthawk WiFi 6 devices, but thought I'd post my most recent headache. My hardware consists of a Motorola MB8600 DOCS 3.1 modem w/...
Well, after three failures in 2 hours I decided to roll back to code .108. I don't recall that code being tempermental in the tail end of last year, but I guess I'll find out soon enough. One thing I did notice is the CPU overhead is much less than when running on code .115. Coincidence? Maybe... Regardless, I'm tempted to do a factory reset again and restore as well, but I'll wait to see if this one fails in the next day.
On another note, while I was waiting for additional failures today I did a little digging that may be helpful as a work around to community. I enabled telnet (Really Netgear??? Not SSH?) by logging into the switch via http://IP_Address/debug.htm. After experiancing a DNS failure, I reset the daemon /etc/init.d/dnsmasq. Viola. The DNS requests/pings to hosts replied again. If code .108 doesn't stop the pain and bleedind, I'll throw a reset in crontab for this until Netgear can debug their buggy code. Or I'll just upgrade again to some true bordline enterprise class gear.
48 hours of stability now after factory reset and minimum configuration changes.
I hadn't tried logging into the router as you did as assumed it was locked down, guess not, will look at that today. From an acceptable work around perspective, it would be great if we could bypass dnsmasq altogether and configure the DNS addresses DHCP server uses. The DNS configuration options in the UI are for upstream DNS, changing DNS servers to google or other provider and has no bearing on the issues as the DNS server address handed out to clients is still the router address proxied through dnsmasq. If we could configure DHCP Options for DNS servers to be somethign other than the router this would bypass the issue. Frankly I'd prefer that confiugration anyway as I'd like to use OpenDNS , Pi-Hole or some other DNS filter software and be able to know what clients are making what DNS calls. As it stands with the Router always being the DNS server PI-Hole for example only shows one client(the router) so some of the benefits are deminished.
Access the router by IP. Support suggested updating the firmware to a beta version. I did it and it initially is working. I'm aware that changing the DNS initself doesn't matter but the action of the update seems to reset the router to temporally correct whatever this bug is.Have a good day. Good luck with our problem
Sorry to say the firmware update failed to resolve the problem