NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RAXE500 New Firmware 1.0.12.96 released
BugFixes: 01/02/2023
Fixes the issue where a configuration through the router web interface causes a port conflict.
Fixes the issue where the router web interface shows that the guest WiFi netw...
After applying this update, the 2.4 GHz band has quit working after a couple of days of operation. Restarting the router restores the 2.4 GHz functionality for a couple of day.
The 5 and 6 GHz band are unaffected.
All of my devices support 5 and or 6GHz bands EXCEPT for my Nest Thermostat and Harmony Elite Remote Hubs(3) which only support 2.4 GHz band (Since I can't move these to other band, I'm forced to restart every couple of days to fix).
This release log for this Firmware updates lists the following know issues;
- Clients cannot connect to the 2.4 GHz band if it functions with a 40 MHz channel width
I hope a fix for this will be forthcoming soon. I would very much like Not to have to restart the router every couple days.
What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and 40 to 48 channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?
Has a power off for 1 minute then back ON with the ISP modem and router been performed since last update?
Be sure to restart your network in this sequence:
Turn off and unplug modem.
Turn off router and computers.
Plug in and turn on modem. Wait 2 minutes for it to connect.
Turn on the router and wait 2 minutes for it to connect.
Turn on computers and rest of network.
Has a factory reset and setup from scratch been performed since last FW update? A complete pull of the power adapters for a period of time after the factory reset then walk thru the setup wizard and setup from scratch with a wired PC and web browser. Recommend setting the default DHCP IP address pool range to the following after applying and a factory reset: 192.168.#.100 to 192.168.#.200.
https://kb.netgear.com/24089/How-do-I-specify-the-pool-of-IP-addresses-assigned-by-my-Nighthawk-router
Would be a first post regarding lost of 2.4Ghz radio. Wouldn't think this is a FW issue right of the bat since others haven't posted about it to date.
TWilson wrote:
After applying this update, the 2.4 GHz band has quit working after a couple of days of operation. Restarting the router restores the 2.4 GHz functionality for a couple of day.
The 5 and 6 GHz band are unaffected.
All of my devices support 5 and or 6GHz bands EXCEPT for my Nest Thermostat and Harmony Elite Remote Hubs(3) which only support 2.4 GHz band (Since I can't move these to other band, I'm forced to restart every couple of days to fix).
This release log for this Firmware updates lists the following know issues;
- Clients cannot connect to the 2.4 GHz band if it functions with a 40 MHz channel width
I hope a fix for this will be forthcoming soon. I would very much like Not to have to restart the router every couple days.
This may be the first report of this that you've seen but according to Netgear's own release notes for Firmware 1.0.12.96 there is a known 2.4 GHz connection issue with it. The 1.0.12.96 firmware release notes clearly state:
Known Issues:
- The Nighthawk app and router web interface don’t successfully complete the OOKLA speed test in PPPoE mode, but the speed test does work normally if you run it from the OOKLA web portal or OOKLA app.
- Clients cannot connect to the 2.4 GHz band if it functions with a 40 MHz channel width.
My 2.4GHz band with current settings has been rock solid since I purchased this router in 2021. This problem appeared within hours of updating to this firmware version and has been re-occurring every few days since after having been restarted to fix. I've reset it to factory defaults and manually reconfigured to no avail.
I'll roll back to the prior version this coming weekend.
Just turn 2.4Ghz to 20Mhz which unless you live in the middle of a field you wont get any benefit from running at 40Mhz anyway. Also most clients tend to support 20Mhz anyway more so IoT devices, it will just cause increased noise levels, less throughput and more interference on your own network let alone your neighbours. Considering the amount of bug fixes in this release plus security updates I think dropping back to 20Mhz is perfectly acceptable, last night I watched a 15Gb film to my Sky Q box over 2.4Ghz (wont use 5 or 6Ghz unless you use Sky as your provider which I don't) and had no issues steaming whatsoever at 20Mhz.
FYI, NG is aware of that issue and is working on it. Hopefully see something in next FW update. Please be patient.
Thank you.
TWilson wrote:
This may be the first report of this that you've seen but according to Netgear's own release notes for Firmware 1.0.12.96 there is a known 2.4 GHz connection issue with it. The 1.0.12.96 firmware release notes clearly state:
Known Issues:
- The Nighthawk app and router web interface don’t successfully complete the OOKLA speed test in PPPoE mode, but the speed test does work normally if you run it from the OOKLA web portal or OOKLA app.
- Clients cannot connect to the 2.4 GHz band if it functions with a 40 MHz channel width.
My 2.4GHz band with current settings has been rock solid since I purchased this router in 2021. This problem appeared within hours of updating to this firmware version and has been re-occurring every few days since after having been restarted to fix. I've reset it to factory defaults and manually reconfigured to no avail.
I'll roll back to the prior version this coming weekend.
Is 20/40Mhz enabled or set for only 40Mhz on this version of FW?
👍
