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/...
First, I don’t need to explain to you why I am using a RAX80 as an AP. However, since you type with such authority as an ‘expert’ in networking equipment, I can tell you that I received it for FFFFFFRRRRRRRRRRREEEEEEEEEEEEEEEEEEE from a friend who went with another vendor.
Second, I’ve had my RAX80 UNGPLUGGED for all of these tests since Sunday and the issue has repeated a dozen times. Tell me again how the different chipsets are the cause of the issue again?
Third, no one on this forum is discussing the details of the .115 beta firmware, only that it is experiencing the same problem as EVERY OTHER CODE TESTED. Stop being a shill for Netgear.
Fourth, if you read the entirety of the posts you will know that myself, and others, have done factory resets and still experience the problem. We are all happy for you and that your RAX120 has no issues whatsoever. Congratulations.
This thread is for people that are having disconnects due to a DNS resolution failure with the RAX120, or those that are willing to work towards a solution. If anyone wants to post something in a lecturing tone like a university professor, don’t waste ours’ or your time. It’s counterproductive.
Code .108 stopped resolving DNS requests at 1am this morning. It made it about 7 hours. Below is a summary of what we’ve seen.
- After 3/1 many users experienced their network devices being disconnected
- It was determined that internal and external hosts could be reached via IP, but DNS in the RAX120 was not functioning
- The problem occurs when DNS servers are set both statically or dynamically in the router.
- The problem occurs regardless of the DNS servers set statically in the router.
- The problem occurs in code levels .108 through .118
- The problem occurs again after a factory reset
- The time between failures varies and the temporary fix is to restart the router (or dnsmasq service)
Since users were hit with this bug without upgrading or making change to their configuration prior to the impact, this feels like a time bomb bug in the code. netgear Are you going to assist your user base? We're hearing a lot of crickets.
, I was going to respond in a similar manner, but.....fanboys.
I really wanted this to work, but my ASUS RT-AX88U arrived this morning and is in service now. Best of luck.
Rax120_rax80, to clarify, when you say that “the problem occurs again after a factory reset,” do you mean that “random disconnects” occur when the RAX120 is in a factory reset state, with all router options having their default values?
Good question. When I said the problem occurs again after a factory reset, the DNS failure that is the root of the issue occurs again. Although, the caveat is I re-apply my configuration from a backup. I haven't left the RAX120 in the default factory configuration, because I have a bunch of clients and it would take e an hour to manually setup the MAC filter again. I can give a factory reset a go and leave the settings default to see if it is any better.
The one thing that stands out to me is that no settings changed for a month before the random DNS failures. Now it's all the time. I would allude it isn't the non-default settings unless there is a time bomb in a particuar setting.