NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Retired_Member
Jun 17, 2020RAX40 Firmware 1.0.3.80 Crash/Bug Log
Hello folks, can everyone please log all the issues they are experiencing with the RAX40 router on 1.0.3.80 firmware under this thread, I see there are several threads going on about the issue, figur...
abelak
Jun 27, 2020Guide
I followed a user's recommendation from another thread and reset the router, installed the latest .80 firmware and reset it again. Set up the router from scratch instead of restoring saved settings.
I then disabled/did not enable the following:
- Smart Connect
- 20/40 MHz coexistence
- Implicit BEAMforming
I enabled WPA2 and WPA3 security.
The router is working fine now. No drops if there is no activity and able to reconnect after going out of range.
Before my earlier post, I had reset the router and setup from scratch and it obviously did not work. I don't know if the combination of steps helped or the change in settings.
If anybody wants to troubleshoot without resetting the router, you could try disabling the 20/40 MHz coexistence (in Advanced --> Wireless Setup) and see if it works. A Google search of the feature led me to an unrelated forum where turning it off helped improve extender connectivity.
rplc
Jun 28, 2020Tutor
I follow the suggestions of abelak and turned the 3 features off. Nows it works perfectly ! Thanks.
Whilst it's good to have a workaround, obviously there are bugs to be fixed and the backup / restore process remains deficient.
- abelakJun 28, 2020GuideI agree rplc. This is not a solution. Just something to ride over until a viable fix is in place.
It’s been almost 2 days now. There are no disconnections so far.- ronald_frJun 28, 2020Luminary
Hello,
I had a stable config with 64 f/w (but with iPhone11 issues and some WAN errors) with
- dedicated channels for WiFi (not auto)
- AIRTIME FAIRNESS disabled
- all other options set (AX, 20/40 coex, BEAMFORMING)
When I tryed 80 f/w with same config it worked between 1/2 - 1 day and then "attached devices" was corrupted and later web interface down...
For now I'll not try 80 f/w anymore and I'll wait for a robust f/w with good fixes and good evolutions.
BR
Ron