The .118 firmware has been giving me DHCP hell or at least I think that is what the issue is where randomly devices seem to be connected (has an IP) but they aren't connected (don't appear when doing a network scan or checking Attached Devices in the GUI).
Upgraded the RAX120 firmware from 1.0.1.118 to 1.0.1.122 using the “ADVANCED | Administration | Firmware Update | Locate and select the upgrade file on your hard disk” process, without performing a factory reset. At present, the router appears to be stable.
Consistent with the observation of dj2819, memory usage appears to have increased by 74MB (without enabling the NETGEAR Armor service).
.122 has been solid for the past couple of days now with a couple exceptions...
Unable to access the USB device using the ReadyCLOUD portal, as reported earlier. (Device access still works.)
Cannot change some device icons via the Nighthawk app. (These devices connect to my Netgear extender.)
I did not do any factor resets, reboots, etc. as part of installing .122. I simply used the "Upgrade" button on the Nighthawk app and, minutes later, it was functioning just fine. YMMV.
For me, the past couple of months or so, .118 has been solid, no disconnects, slow-downs, reboots, spurious factory resets, etc. If have no explanation as to why things settled down for me. I was having these issues when I initially installed .118. After a couple of pin-hole factory resets, the router finally just settled down and I've not had a single issue, not one, for quite a few weeks now. I've never rebooted the router myself during all this time.
I'm certainly not letting Netgear off the hook for what they put me through when I initially purchased the RAX120, but it's looking solid the past couple months or so. So for those out there still hoping not to brick this thing, "I've been where you are. I don't know what I did to fix it. It just starting working."
My suspicion is that it mighthave been this sequence that I eventually executed...
Pin-hole factory reset on the old firmware.
Upgrade to the new firmware.
Pin-hole factory reset on the new firmware.
Pin-hole factory reset on the new firmware again.
Configure your router from scratch. Don't restore from any config files
So far .122 has been stable. The issues I been having had nothing to do with firmware versions but DHCP issues I believe. Started a seperate discussion here if anyone has the same issue.
Has anyone figured out the ReadyCloud issue on this latest version of the fimware (.122)? ReadyCloud can no longer access my attached USB drive. Apparently this is a known issue.
.122 has been stable for the most part and the fix for DoS attacks in the logs looks like its fixed because I saw a lot more DoS logs than before.
However my issues with the DHCP server were not fixed and still had those same issues. I was able to resolve those by just switching the RAX120 to AP mode and using a EdgeRouter X as the DHCP server that seems to work really well. Still can't believe I paid $400 for a router that can't behave as a router...
Interesting that with .122 with DHCP enabled used 420-430mb of ram. With DHCP off it only uses 360-380mb of ram. Didn't know the DHCP server would take up so much memory.
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?
I'm using an RAX120 and EX8000 for my home networking
I have tried twice now to upgrade to 1.0.1.122 and find it extremely unstable. 1st time just and upgrade 2nd time upgrade then factory reset and reconfigure
I have ~45 devices and everything worked fine, no isuues with 1.0.1.118
With 1.0.1.122 I lose internet connectivity at least 10 times a day, which really sucks trying to work from home.
I have downgraded back to 1.0.1.118 for stability and sanity's sake
The worst update I have ever installed on any netgear produccts. I don't know if it has to do with the new Armor security but it's awful
I'm having DNS issues with this router for almost a year. Any firmware revision (going all the way back to .62) results in the same issue. As I bought it last year, its now a $400 paperweight. No help, no solutions, just a lousy product. The last netgear product Ill ever buy.
New firmware run to a issue that can’t copy file to usb device using iOS Files App, anyone with same issue? Iphone pop a window says Bad file descriptor
After upgrading to 1.0.1.122 my Attached Devices page is showing blank as well. Same for the Nighthawk app. The number of devices on both the website and app are populated.
I tried performing a factory reset after a few days, but am seeing the same results as above. It's been over 24 hours since I performed the factory reset. I thought it may take a little time for the information to populate, but that doesn't seem to be the case.
My RAX120 USB device work normally when I use Mac Samba to access, but when I use iOS to access, it’s normal to read file, but it’s can’t copy files from iOS to USB, neither copy or duplicate files inside USB, says “Bad file descriptor”, I tried to roll back the firmware to 118 version and test it, nothing changed, I’m confused.
