NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
New - RAXE500 Firmware Version 1.0.10.82 Released
New Features:
- Supports QoS
- Supports Smart Parental Control (SPC)
- Supports WPA2/WPA3 mixed mode
Security Fixes:
- Fixes security vulnerabilities.
For more information about security vulnerabilities, visit https://www.netgear.com/about/security/
Bug Fixes:
- Fixes ReadyShare add/edit/browse folder issue
- Fixes IP address reservation cap of only up to 64 issue
Firmware Update Instructions:
Download Link:
https://www.netgear.com/support/product/raxe500.aspx#download
To update your router’s firmware, follow the instructions in your router’s user manual. To view your router’s user manual, visit https://www.netgear.com/support/product/RAXE500.aspx#docs
NOTE: Nighthawk app or the routers web page may not report seeing new FW updates. NG may not push this to there auto update services immediately and may activate the newer FW update being seen on there auto update services at a later time. User will have the choice to manually update if you want too.
Manually update FW on the router if this isn't seen on the routers web page:
https://kb.netgear.com/23960/How-do-I-manually-update-the-firmware-on-my-NETGEAR-router
NOTE: Use a wired PC and web browser to update router FW. If continued problems are seen after a FW update, it's recommended to try a factory reset and setup from scratch with out loading any saved configurations from backup files.
https://kb.netgear.com/9665/How-do-I-perform-a-factory-reset-on-my-NETGEAR-router
This article applies to:
Let us know how it works for you...Please leave feedback.
16 Replies
Replies have been turned off for this discussion
Excellent. This is a really important firmware update feature-wise. I was waiting on both QoS and Smart Parental Controls. I updated a few days ago and so far everything seems to be working as expected. I hosted a full-day Zoom event yesterday with zero disconnections. QoS and SPC were both enabled. Nice work! Thank you!
Thanks for the feedback. Glad it working well. Be sure to save off a back up configuration to file for safe keeping. Saves time if a reset is needed.
https://kb.netgear.com/000062080/How-do-I-back-up-the-configuration-settings-on-my-Orbi-WiFi-System
Enjoy. 📡Backup taken. Thank you for the reminder. I have been running this firmware now for a couple of weeks since its launch. It has been very stable. I did some testing regarding QoS and it seems to be working properly. In addition, I purchased SPC and that too is working properly. Thanks again for a great release!
After updating to this firmware and enabling WPA2/WPA3 mixed mode, I was surprised that several mobile devices started to complain that my network was hidden, despite SSID Broadcast being enabled on all bands. On performing a WiFi scan, I found that the Guest networks were up and running in hidden mode despite never being enabled. On a hunch I initialized all the Guest networks with non default values, left them disabled, and restarted. The primary SSIDs were no longer hidden and the guest SSIDs were no longer present. Weird.
There still seems to be no obvious means to set the DHCP lease interval, packet tracing on previous builds suggest those builds were using a default value equivalent to 24 hours. I suspect this is still the case with this build. A 24 hour lease time is a fine default for a commercial environment, but Apple and Google both recommend a default of 8 hours for non commercial use. If anyone knows of a means to either view or change the lease interval, that'd be appreciated. A too long lease interval can result in a DHCP request being refused, resulting in a device not receiving an IP address. This might not be an issue in environments with a few handfuls of devices, but is a significant issue in setups with many dozens of devices.
Many of the help screens are still quite incomplete, in Basic and Advanced web admin modes.
Did you factory reset and setup the router after you applied this version of FW?
Screen captures of what your seeing would be helpful.What Browser are you using?
Tonkinite wrote:
After updating to this firmware and enabling WPA2/WPA3 mixed mode, I was surprised that several mobile devices started to complain that my network was hidden, despite SSID Broadcast being enabled on all bands. On performing a WiFi scan, I found that the Guest networks were up and running in hidden mode despite never being enabled. On a hunch I initialized all the Guest networks with non default values, left them disabled, and restarted. The primary SSIDs were no longer hidden and the guest SSIDs were no longer present. Weird.
There still seems to be no obvious means to set the DHCP lease interval, packet tracing on previous builds suggest those builds were using a default value equivalent to 24 hours. I suspect this is still the case with this build. A 24 hour lease time is a fine default for a commercial environment, but Apple and Google both recommend a default of 8 hours for non commercial use. If anyone knows of a means to either view or change the lease interval, that'd be appreciated. A too long lease interval can result in a DHCP request being refused, resulting in a device not receiving an IP address. This might not be an issue in environments with a few handfuls of devices, but is a significant issue in setups with many dozens of devices.
Many of the help screens are still quite incomplete, in Basic and Advanced web admin modes.
No, I didn’t factory reset the router before this issue. Does the router factory reset itself when it auto updates it’s own firmware? I can’t recall any instances where factory reseting resolved issues like this, and I’ve owned Netgear routers for over five years.
I took very few screenshots of the problem while it was happening, I suspect that it is related to the guest networks being in default state. I’m just reporting the issue in case someone else has something similar happen. I did take a few showing the hidden network warning on iOS.
I used the Safari browser on macOS Monterey, I hope Netgear QA is testing browsers other that Edge or Chrome. I’m not sure how that’s relevant in this instance.
