NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RAXE500 Beta FW v1.0.9.72 is available for Testing
Hello RAXE500 Community,
We have a beta firmware available for testing for the RAXE500 that we hope will resolve some of the instability issues that have been reported over the last few months.
Please note: We are still working on a patch for a reported 2.4GHz connectivity issue with Nest cameras and hope to have that released as quickly as possible in the upcoming weeks.
Release notes:
- New
- (new) supports dynamic QoS
- (new) security enhancement - webGUI login password enhancement
- (new) security enhancement – login blockout when consecutive password failed multiple times
- (new) support DNS over https
- Fix
- (fix) fixes some security vulnerability issues
- (fix) add patches to improve system stability
FW:
We're looking forward to hearing feedback on this firmware and if all goes as expected we can publish it as an official release.
Best,
ChristineT
29 Replies
Replies have been turned off for this discussion
I can confirm with v1.0.1.52 and v1.0.9.72 that my Intel AX210 6Ghz PCI adapter (v22.45) install using Windows 10x64 is NOT connecting to the RAXE500 when WPA3 is enabled. I can connect the adapter to the RAXE500 if I disable WPA3 and set for OPEN security.
Same Intel AX210 adapter works on a different NG router with WPA3 enabled.
Adapter connected to NG non RAXE500 router using WPA3:
Microsoft does not support WPA-SAE H2E feature on current win10 so you will need to ugprade your OS to win11 in order to support it (this is kind of Micrsoft's strategic to encourage people to upgrade to win11 to gain the win11 usage.)
If you still like to connect it in win10, you will need to use beta version (https://insider.windows.com/en-us/ ) with specific AX210 driver.
Would be interested to know then why does Intel release Windows 10 and 11 drivers for AX210 6Ghz adapters?
I just downloaded v22.90 yesterday...
Altsai wrote:
Microsoft does not support WPA-SAE H2E feature on current win10 so you will need to ugprade your OS to win11 in order to support it (this is kind of Micrsoft's strategic to encourage people to upgrade to win11 to gain the win11 usage.)
If you still like to connect it in win10, you will need to use beta version (https://insider.windows.com/en-us/ ) with specific AX210 driver.
I'm getting an "Invalid Uplink Bandwidth" error when trying to enable QOS. I'm also getting intermediate drops in connectivity (I can't even ping the router) every 10 mins or so with the latest non beta firmware. I've had nothing but issues with this router, and I'm always suprised when it's works normal.
Have you factory reset the router and setup from scratch along with powering OFF the ISP modem for 1 minute then back ON and complete the setup on the router?
What browser are you using?
I'm using Chrome. I'll try doing the factory reset. It's upsetting I have to wipe a router to get it to work properly.
Do not see such issue. You may provide related debugging log for NTGR support team to check.
Thanks for letting me know. I will try out the new Firmware
Item 1
I still experience the same frequent client disconnects using the beta firmware that I experienced in prior firmware in the 5GHz band even with its Mode set to "Up to 2400 Mbps" and channel set to 44 (non-DFS channel).This only occurred with my prior RAX200 when its Mode was set to "up to 4800 Mbps" due to Dynamic Frequency Selection (DFS). When I changed the RAX200 Mode to "Up to 2400 Mbps" and selected a non DFS channel, the disconnects stopped occurring (I live near an airport so I assume DFS was sensing a radar and was switching channels resulting in client disconnections).
With the RAXE500, changing the 5HGZ band mode to "Up to 2400 Mbps" and selecting a non DFS channel hasn't resolved the client disconnects (like it did with my prior RAX200).
Not happy about this and am considering returning the RAXE500 and rolling back to the RAX200 because of this and item 2 below.
Item 2
The 6GHz band is working with my Windows 11 devices having the Intel AX210NGW adapter using WPA3 on 6GHz.Range is horrible though. I get 3 bars when 15-20 feet away in line of sight. Connection speeds are also frequently the same as or lower than what I get when connected to the 5Ghz band.
The 6GHz radio power output seems to be much lower than the 5GHz radio (I know there is greater attenuation across materials when using 6 GHz vs 5 GHz and 2.4 GHz - however I'm observing this with line of slight with only air between the router and device).
I had much higher hopes for 6Ghz band than this (The marketing for has been extremely over hyped). I currently have the entire 6GHz band to myself in my neighborhood and its typical performance isn't any better than what I get on the congested 5GHz band (was expecting to see improved data transfer ratperformance between 6GHz AX clients and file/applications servers attached to local network).
Item 3
The beta firmware included support for QOS. When I select the QOS setting page, I see options to enable WMM for 2.4 GHz, 5 GHz, and 5GHz-2. By default, WMM is checked for 2.4GHz and 5GHz (5GHz-2 is not checked).Obviously, there shouldn't be any settings for 5GHz-2 and instead should be settings for the 6GHz band.
I haven't tested if QOS works on 2.4 or 5 GHz bands.
Thank you for all the feed back I forward this to our engineers.
DarrenM
TWilson wrote:
Item 1
I still experience the same frequent client disconnects using the beta firmware that I experienced in prior firmware in the 5GHz band even with its Mode set to "Up to 2400 Mbps" and channel set to 44 (non-DFS channel).This only occurred with my prior RAX200 when its Mode was set to "up to 4800 Mbps" due to Dynamic Frequency Selection (DFS). When I changed the RAX200 Mode to "Up to 2400 Mbps" and selected a non DFS channel, the disconnects stopped occurring (I live near an airport so I assume DFS was sensing a radar and was switching channels resulting in client disconnections).
With the RAXE500, changing the 5HGZ band mode to "Up to 2400 Mbps" and selecting a non DFS channel hasn't resolved the client disconnects (like it did with my prior RAX200).
Not happy about this and am considering returning the RAXE500 and rolling back to the RAX200 because of this and item 2 below.
>>>> did you ever try other channels in other bands? e.g., 5G band 4 (non-DFS channnels)?
Item 2
The 6GHz band is working with my Windows 11 devices having the Intel AX210NGW adapter using WPA3 on 6GHz.Range is horrible though. I get 3 bars when 15-20 feet away in line of sight. Connection speeds are also frequently the same as or lower than what I get when connected to the 5Ghz band.
The 6GHz radio power output seems to be much lower than the 5GHz radio (I know there is greater attenuation across materials when using 6 GHz vs 5 GHz and 2.4 GHz - however I'm observing this with line of slight with only air between the router and device).
I had much higher hopes for 6Ghz band than this (The marketing for has been extremely over hyped). I currently have the entire 6GHz band to myself in my neighborhood and its typical performance isn't any better than what I get on the congested 5GHz band (was expecting to see improved data transfer ratperformance between 6GHz AX clients and file/applications servers attached to local network).
>>>>> FCC only opens LPI (low power mode) for 6GHz band so yes, the RF output power is actually lower than 5GH band. And 6GHZ RF power drop is faster than 5GHZ band which is the physical limitation.
Item 3
The beta firmware included support for QOS. When I select the QOS setting page, I see options to enable WMM for 2.4 GHz, 5 GHz, and 5GHz-2. By default, WMM is checked for 2.4GHz and 5GHz (5GHz-2 is not checked).Obviously, there shouldn't be any settings for 5GHz-2 and instead should be settings for the 6GHz band.
>>>> I agree. seems like GUI issue which needs to be fixed.
I haven't tested if QOS works on 2.4 or 5 GHz bands.
Altsai wrote:
TWilson wrote:Item 1
I still experience the same frequent client disconnects using the beta firmware that I experienced in prior firmware in the 5GHz band even with its Mode set to "Up to 2400 Mbps" and channel set to 44 (non-DFS channel).This only occurred with my prior RAX200 when its Mode was set to "up to 4800 Mbps" due to Dynamic Frequency Selection (DFS). When I changed the RAX200 Mode to "Up to 2400 Mbps" and selected a non DFS channel, the disconnects stopped occurring (I live near an airport so I assume DFS was sensing a radar and was switching channels resulting in client disconnections).
With the RAXE500, changing the 5HGZ band mode to "Up to 2400 Mbps" and selecting a non DFS channel hasn't resolved the client disconnects (like it did with my prior RAX200).
Not happy about this and am considering returning the RAXE500 and rolling back to the RAX200 because of this and item 2 below.
>>>> did you ever try other channels in other bands? e.g., 5G band 4 (non-DFS channnels)?
>>>> Yes. Also tried 153 with the same results. Lowering mode and using non-DFS channel significantly reduced the frequency of client disconnects but has not resolved it like it did with my RAX200. The latest RAX200 firmware is much more stable/reliable as compared to the RAXE500 firmware (which to me, is more like alpha code with incomplete feature set - e.g. a work in progress).
Item 2
The 6GHz band is working with my Windows 11 devices having the Intel AX210NGW adapter using WPA3 on 6GHz.Range is horrible though. I get 3 bars when 15-20 feet away in line of sight. Connection speeds are also frequently the same as or lower than what I get when connected to the 5Ghz band.
The 6GHz radio power output seems to be much lower than the 5GHz radio (I know there is greater attenuation across materials when using 6 GHz vs 5 GHz and 2.4 GHz - however I'm observing this with line of slight with only air between the router and device).
I had much higher hopes for 6Ghz band than this (The marketing for has been extremely over hyped). I currently have the entire 6GHz band to myself in my neighborhood and its typical performance isn't any better than what I get on the congested 5GHz band (was expecting to see improved data transfer ratperformance between 6GHz AX clients and file/applications servers attached to local network).
>>>>> FCC only opens LPI (low power mode) for 6GHz band so yes, the RF output power is actually lower than 5GH band. And 6GHZ RF power drop is faster than 5GHZ band which is the physical limitation.
>>>> I understood this but did not fully appreciate the impact of this limitation until after deployment (marketing hype led me to believe it would perform better than it actually does in the real world - had expected reduced range but not near as bad is it actually is). Good article explaining 6E power levels here: https://www.extremenetworks.com/extreme-networks-blog/wi-fi-6e-its-not-just-about-6ghz/
IMHO, Netgear (and others) are greatly overhyping/exaggerating the benefits of 6E in their product marketing. As of today, 6E is not able to deliver on its promised benefits outside of a lab or very narrow window of environments having ideal conditions (e.g. client is extremely close to and in line of sight of the router). In a typical home or business, you’re better off sticking to 5GHz today. Maybe this will improve if the FCC allow the power to be increased in the future (not crossing my fingers that it will ever be increase though) ....Item 3
The beta firmware included support for QOS. When I select the QOS setting page, I see options to enable WMM for 2.4 GHz, 5 GHz, and 5GHz-2. By default, WMM is checked for 2.4GHz and 5GHz (5GHz-2 is not checked).Obviously, there shouldn't be any settings for 5GHz-2 and instead should be settings for the 6GHz band.
>>>> I agree. seems like GUI issue which needs to be fixed.
I haven't tested if QOS works on 2.4 or 5 GHz bands.
Hi all,
I live in France and, till now, I was not able to detect and use the 6GHz band on my Samsung S21 ultra.
I installed the new firmware on my RAXE500 (bought in the USA) and unfortunately, it did not change anything for me.
Will a new firmware be necessay to "open" the 6GHz band in France ? If yes, do you know when this new firmware is available ?
Regards,
Franck
Possible that your regiona may not support 6Ghz.
Is the 6Ghz wireless setting not seen on the routers web page under Basic tab/Wireless Settings?
We don't get information on if or when new FW or FW features are forth coming.
golways wrote:
Hi all,
I live in France and, till now, I was not able to detect and use the 6GHz band on my Samsung S21 ultra.
I installed the new firmware on my RAXE500 (bought in the USA) and unfortunately, it did not change anything for me.
Will a new firmware be necessay to "open" the 6GHz band in France ? If yes, do you know when this new firmware is available ?
Regards,
Franck
the 6Ghz wireless setting is seen on the routers web page under Basic tab/Wireless Settings and on.
6Ghz band is now authorized in Europe and France and RAXE500-100EUS can now be preordered on Netgear french website (delivery on mid-january).
golways wrote:
Hi all,
I live in France and, till now, I was not able to detect and use the 6GHz band on my Samsung S21 ultra.
>>>>>> S21 ultra does not support WiFi 6E. Only S21 Ultra 5G support wifi 6E. And France just opened 6GHZ band so would still need samsung to release new image to support 6E for S21 Ultra 5G.
I installed the new firmware on my RAXE500 (bought in the USA) and unfortunately, it did not change anything for me.
Will a new firmware be necessay to "open" the 6GHz band in France ? If yes, do you know when this new firmware is available ?
Regards,
Franck
A few observations:
On the 6ghz settings, if i choose a XX(PSC) channel, i am not able to connect mobile or any devices. If i choose one without, i am able to connect, as well the devices can see the SSID of that radio.
Seperately, after running for some time, it takes a reboot before devices can see the SSID for 6ghz.
My laptop with a genuine AX210 adapter, running Windows 11 Pro saw the 6ghz one time and were able to connect. After a reboot of the machine, i a no longer able to see this network again. I have removed the adapter physically, removed ghost entries in the registry, and re added, with no luch.
