NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Killhippie's avatar
Killhippie
Prodigy
Jan 02, 2023

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 network is active even though you set up a WiFi schedule that specifies that the guest WiFi network must be inactive during that time.
  • Fixes the issue where the router has low throughput when QoS is enabled.
  • Fixes the issue where you cannot use the Nighthawk app to pause or restart parental controls for a client if you already blocked the client in the router web interface.
  • Fixes the issue where you might be unable to select certain 5 GHz channels if the country setting is Australia.
  • Fixes the issue where the router can’t send the log via Outlook.
  • Fixes the issue where the router does not send the log if you configure the option to send the log when it is full. 
  • Fixes the issue where all Ethernet LAN ports go down if you change the Internet subnet mask.
  • Fixes the issue where the link aggregation options are masked in the router web interface when the router functions in access point (AP) mode.
  • Fixes the issue where the router web interface shows a warning message when you select port 1 or the Multi-Gig port in VLAN bridge mode.
  • Fixes the issue where admin password protection is not enabled by default for ReadyShare HTTPS (via Internet) and FTP (via Internet).
  • Fixes the issue where access point (AP) mode is not masked in the router web interface when WAN aggregation is enabled.
  • Fixes the issue where the router web interface doesn’t show MAC address information on the Attached Devices page when QoS is enabled
  • Fixes the issue where the router web interface displays an incorrect text format.
  • Fixes the issue where the router allows the user name and password for PPPoE to be longer than 63 characters.

Security Fixes:

  • Fixes security vulnerabilities.

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.

 

Download Link:

https://www.netgear.com/support/product/raxe500.aspx#download

 

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

 

https://kb.netgear.com/24231/How-do-I-back-up-the-router-configuration-settings-on-my-Nighthawk-router

 

NOTE: 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.

 

Cooling: Its recommended to install a USB laptop cooler under the router for 24/4 cooling. Helps keep the router cool and helps avoid heat damage to the electronics.

 

This article applies to:

 

Let us know how it works for you...

47 Replies

  • Yay, new firmware update. RAXE500 Firmware Version 1.2.13.100

    Bug Fixes:

    Fixes the issue where Anywhere Access doesn’t work when Web Services Management is turned on.
    Fixes the issue where the on-board log doesn’t automatically clear after logs are emailed.
    Fixes the issue where the download and upload values shown by the built-in speed test are lower than the actual line rate.
    Fixes the issue where the 2.4G band doesn’t switch to 40 MHz when 2.4G 20/40 MHz Coexistence is disabled.
    Fixes the issue where iPhones cannot connect to the 2.4G guest SSID successfully when WPA3 encryption is enabled.
    Fixes the issue where the Nighthawk App shows errors when onboarding with PPPoE.
    Fixes the issue where Nighthawk App users see the “Something went wrong” error message when trying to enable Anywhere Access.
    Fixes the issue with low performance when Port Aggregation LACP mode is enabled.
    Fixes the issue where port forwarding doesn’t work when the port range is set to 20-22.


    https://community.netgear.com/t5/Nighthawk-with-WiFi-6-AX-and/RAXE500-New-Firmware-Version-1-2-13-100-Released-firmware/td-p/2350824

  • Why no new firmware? It has almost been a year since we have gotten a firmware update on this product.

    • michaelkenward's avatar
      michaelkenward
      Guru

      strykerzr350 wrote:

      Why no new firmware? It has almost been a year since we have gotten a firmware update on this product.


      Maybe there is no need. If the current version has no problems and there are no serious security issues that need mending, why put people through the hassle? Updates are not without their own risks.

       

      • p0se1d0nX's avatar
        p0se1d0nX
        Star
        Exactly! Really don’t want Netgear heading down the same downward spiral path as Asus where they do weekly updates that fixes something and breaks several others in the process. No thank you!

        I left Asus years ago and never looked back for this reason. Who the heck needs weekly fw updates? Talk about over kill.
    • FURRYe38's avatar
      FURRYe38
      Guru

      Only been 9 months. 

      Something not working for your with your RAXE500? 

      • strykerzr350's avatar
        strykerzr350
        Guide
        Everything is working fine with it, just the wireless lights and internet lights does not blink as advertised.

  • I’m having a very odd issue with my RAXE500. Basically I can’t use my ISPs DNS. If I do the orange light comes on, it repeatedly says it’s disconnecting from the Internet, even though it doesn’t actually register that in the logs, I think just becomes really slow, or acts like a stale dns, even if I enter them manually, it doesn’t work. However, I can use cloud flare or any other DNS and it works perfectly okay so I’ve got no idea what’s going wrong here, I spoke to my ISP who said there’s nothing wrong at their end. I’ve tried an old are we rax120 and that showed up the same symptoms basically it said there was no Internet but there was but it was excruciatingly slow and it kept dropping Internet connectivity, but that still didn’t show up in the logs , no idea what’s going on why it works on any other DNS service apart from my own ISPs DNS.

     

     Also have Netgear given up on updating any of the Wi-Fi 6/6E router firmware it seems like most devices have been not been updated this year and there are bugs with the RAXE500 that really do need sorting out. It’s a bit like the RAX120 doesn’t have the firmware version that is supposed to be there to fix version v2 issues. It’s still got a version that’s really old that doesn’t fix that issue properly. Are Netgear actually posting new firmware, or is it that they just rushing to get Wi-Fi seven gear out?  

    • FURRYe38's avatar
      FURRYe38
      Guru


      What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?

       

      I'm using my RAXE500 with auto detected ISP DNS and Internet LED is on constant WHITE here. My RAXE is connected to a CAX80 cable modem in modem only mode. 

       


      Killhippie wrote:

      I’m having a very odd issue with my RAXE500. Basically I can’t use my ISPs DNS. If I do the orange light comes on, it repeatedly says it’s disconnecting from the Internet, even though it doesn’t actually register that in the logs, I think just becomes really slow, or acts like a stale dns, even if I enter them manually, it doesn’t work. However, I can use cloud flare or any other DNS and it works perfectly okay so I’ve got no idea what’s going wrong here, I spoke to my ISP who said there’s nothing wrong at their end. I’ve tried an old are we rax120 and that showed up the same symptoms basically it said there was no Internet but there was but it was excruciatingly slow and it kept dropping Internet connectivity, but that still didn’t show up in the logs , no idea what’s going on why it works on any other DNS service apart from my own ISPs DNS.

       

       Also have Netgear given up on updating any of the Wi-Fi 6/6E router firmware it seems like most devices have been not been updated this year and there are bugs with the RAXE500 that really do need sorting out. It’s a bit like the RAX120 doesn’t have the firmware version that is supposed to be there to fix version v2 issues. It’s still got a version that’s really old that doesn’t fix that issue properly. Are Netgear actually posting new firmware, or is it that they just rushing to get Wi-Fi seven gear out?  


       

  • Three (maybe four bugs) bugs I've found with this firmware:

     

    First bug:

     

    WiFi 6E still "crashes", basically new clients cannot connect to the 6E SSID, while existing clients that are already connected to the 6E SSID remain connected, if I disconnect and reconnect and existing client, it can no longer connect to the 6E SSID, etc. the only solution I've come up with is just to reboot the RAXE500 and after it starts up everything is good again.  The 2.4 and 5ghz bands continue to work while the 6E SSID is not allowing new connections.

     

    Second bug:

     

    After setting the RAXE500 to an Access Point, the Internet option under Basic on the web client is grayed out.  The workaround is to make any setting changes to Internet before you change it from a router to an Access Point.

     

    Third bug:

     

    On the NightHawk app on my mobile device (both on Android and on iPhone), under Settings, Router Settings, Internet Port, it says the "Type" is "Down", so it's not reporting properly as I'm using the 5th port for Internet access and not the "Yellow" port.  My device is setup for Access Point mode (see next potential bug below).

     

    Fourth bug (maybe):

     

    I have the RAXE500 connected to a Netgear M4250-12M2XF through the 5th port labelled multi gig, it will only detect it as a 1GB connection, I have plugged other devices that are 2.5G capable into the same cable and they all detect at 2.5G, etc.  I set the 5th port up as the Internet port instead of using the Yellow port if that makes any difference in why I'm getting this bug.

     

    • FURRYe38's avatar
      FURRYe38
      Guru

      rsun0525 wrote:

      Three (maybe four bugs) bugs I've found with this firmware:

       

      First bug: TBT

       

      WiFi 6E still "crashes", basically new clients cannot connect to the 6E SSID, while existing clients that are already connected to the 6E SSID remain connected, if I disconnect and reconnect and existing client, it can no longer connect to the 6E SSID, etc. the only solution I've come up with is just to reboot the RAXE500 and after it starts up everything is good again.  The 2.4 and 5ghz bands continue to work while the 6E SSID is not allowing new connections.

      Haven't tested this as of yet. Will check this as I get time.

       

      Second bug: NOT A BUG.

       

      After setting the RAXE500 to an Access Point, the Internet option under Basic on the web client is grayed out.  The workaround is to make any setting changes to Internet before you change it from a router to an Access Point.

      SInce the router in AP mode has most of it's router and internet configuration features disabled, NG only chooses to display the informational tiles on this screen when in AP or Bridge mode, thus not a bug:

       

      Third bug: NOT A BUG.

       

      On the NightHawk app on my mobile device (both on Android and on iPhone), under Settings, Router Settings, Internet Port, it says the "Type" is "Down", so it's not reporting properly as I'm using the 5th port for Internet access and not the "Yellow" port.  My device is setup for Access Point mode (see next potential bug below).

      I did see this once, however, I had not put the WAN cable from my host router into the WAN port. After I moved the cable over to the yellow WAN port, the NH app reported the TYPE as DHCP:

      This is Router Mode:

       

      This is AP mode. Both seen in router mode and in AP mode. 

      Currently in AP mode with RAXE connected to a GS110MX multgig switch:

       

      Fourth bug (maybe): Not Reproducing/Not a bug.

       

      I have the RAXE500 connected to a Netgear M4250-12M2XF through the 5th port labelled multi gig, it will only detect it as a 1GB connection, I have plugged other devices that are 2.5G capable into the same cable and they all detect at 2.5G, etc.  I set the 5th port up as the Internet port instead of using the Yellow port if that makes any difference in why I'm getting this bug.

      I first tested the RAXE in both Router and AP mode behind a 1Gb LAN switch using the MG port:

      I then tested the RAXE in AP Mode behind a CAX80 cable modem on it's MP Port: LAN5

      And now currently with a NG GS110MX multi gig switch in between the CAX80 and RAXE. 

      Both configurations show 2.5Gb on the RAX500 MG port:

      I did remember that to get the MG port to be enabled correctly for AP or Bridge mode, you first have to enabled the MG port on the RAXE while in router mode, once it's enabled there, then you can configure AP or Bridge mode on the RAXE and then connect it up on the MG port.

       

      I'll leave it run so I can observe some 6Ghz behaviors though not sure if I can reproduce anything as I don't have many 6Ghz devices.


       

      • rsun0525's avatar
        rsun0525
        Guide

        So after moving the back and forth between the Internet port and port 5, it's now showing up as 2.5G, so now the last problem I have is once in a while the 6G band "dies" and doesn't accept any new connection, so only way to solve is to reboot.

    • FURRYe38's avatar
      FURRYe38
      Guru

      rsun0525 wrote:

      Three (maybe four bugs) bugs I've found with this firmware:

       

      First bug:

      WiFi 6E still "crashes", basically new clients cannot connect to the 6E SSID, while existing clients that are already connected to the 6E SSID remain connected, if I disconnect and reconnect and existing client, it can no longer connect to the 6E SSID, etc. the only solution I've come up with is just to reboot the RAXE500 and after it starts up everything is good again.  The 2.4 and 5ghz bands continue to work while the 6E SSID is not allowing new connections.

      What channel are you using on 6ghz? 

      What 6Ghz supporting devices do you have connected? 

       

      Second bug:

      After setting the RAXE500 to an Access Point, the Internet option under Basic on the web client is grayed out.  The workaround is to make any setting changes to Internet before you change it from a router to an Access Point.

      What port are you using when your in AP mode? Main Yellow WAN port or the Multi-Gig port? 

      Does this happen in both WAN or Multigig ports? 

       

      Third bug:

      On the NightHawk app on my mobile device (both on Android and on iPhone), under Settings, Router Settings, Internet Port, it says the "Type" is "Down", so it's not reporting properly as I'm using the 5th port for Internet access and not the "Yellow" port.  My device is setup for Access Point mode (see next potential bug below).

      Does the Internet port report status as UP when using the yellow WAN port and not the MultiGig port? 

       

      Fourth bug (maybe):

      I have the RAXE500 connected to a Netgear M4250-12M2XF through the 5th port labelled multi gig, it will only detect it as a 1GB connection, I have plugged other devices that are 2.5G capable into the same cable and they all detect at 2.5G, etc.  I set the 5th port up as the Internet port instead of using the Yellow port if that makes any difference in why I'm getting this bug.

      Do other mutli gig supporting devices, i.e. PC or other switches connected to the MultiGig port on the RAXE show 2.5Gb or do all devices report the lower 1Gb speed when connected to the RAXE MutliGig port?

       


       

      • rsun0525's avatar
        rsun0525
        Guide

        For the 6Ghz stuff I have it set to the following:

        Channel: 37(PSC)

        Mode: Up to 4800 Mbps

        Security Options: WPA3-Personal

         

        I'm using the multi-gig port (5) for the Internet, nothing is plugged into the "Yellow" port.

         

        It reports as Down.

         

        I have other 2.5GB devices plugged into my M4250-12M2XF, I tried multiple ports from the M4250-12M2XF that were all showing 2GB before with the previous devices, but did not plug any other 2.5GB device into the RAXE500, since I'm trying to use it for my main WiFi router, I don't have time to keep my entire home "down" during this process, I can say I'm almost at a point where I want to switch back to my eero 6e pro or Asus ZenWiFi Pro ET12 which both worked just fine at 2.5GB with that cable and port, etc. and just accept the RAXE500 is just too buggy and lack of recent firmware updates tells me maybe they've moved on from this device.


    • rsun0525 wrote:

      Second bug:

       

      After setting the RAXE500 to an Access Point, the Internet option under Basic on the web client is grayed out.  The workaround is to make any setting changes to Internet before you change it from a router to an Access Point.

       

      That is "as designed":

       

      Disabled Features on the Router when set to AP Mode | Answer | NETGEAR Support

       

      Then again, that KnowledgeBase article is itself inaccurate in places. (It is wrong about the Guest Network.)

       

       

  • Router still has an issue when using the readyshare feature with the new firmware. Disabling the AX mode and the OFDMA will stop the router software from spazzing out and becoming unresponsive, but the router continues to drop the Internet connection, and the wifi signals drop out every 20 seconds or so. Only thing that causes issue to go away, is to unplug the external hdd from the routers USB port. This issue is occurring even if there is no device that is trying to access the external hdd.

    • phrostb's avatar
      phrostb
      Star

      Just bought one of these on ebay for $200. Set it up. Seems decent so far. I wanted something relatively simple yet modern. I noticed a few settings aren't enabled by default.

       

      Disabled by default:
      MU-MIMO
      OFDMA in 2.4 GHz and 5 GHz
      Smart Connect band steering, which requires the same SSID for 2.4 GHz and 5 GHz

       

      Should I be turning these on? I live in a one floor condo of around 1500 Sq. Ft. Desktop and a few other devices on ethernet. I have a couple laptops and a few cell phones. None of them support wifi 6E yet. Any opinions? I'm thinking Smart Connect at least...

      • FURRYe38's avatar
        FURRYe38
        Guru

        You can try them all one then disable the ones you may not need or use or seems to cause problems. Most newer devices in past few year should all support MIMO so you can enable this and see. 

  • 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.   

    • FURRYe38's avatar
      FURRYe38
      Guru

      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.   


       

      • TWilson's avatar
        TWilson
        Aspirant

        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.

  • Retired_Member's avatar
    Retired_Member

    NOTE: 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.

     

    I am wondering why this recommendation, as I've also seen it for other models. Any thoughts?

    • Tonkinite's avatar
      Tonkinite
      Luminary

      I have been using 10.1.1/24 for years and have had no serious issues for this model, it’s also a great deal easier to type out the IP4 addresses with this range.

       

      I hope that the built in DHCP service doesn’t have some hardcoded mess inside that prioritizes the 100 to 200 range for the 192.168/16 subnet, or any other subnet for that matter.

       

      I’d also appreciate a clarification on this point.

      • FURRYe38's avatar
        FURRYe38
        Guru

        The 100-200 range is just a recommendation only. Personal experience brought over from other brand router mfr I used for years as there default range. Worked well for me  there and works for my needs on NG routers. Gives room for static IP assigned devices on ether side of the pool as well. Also less to handle in regards for the router management with a smaller IP address pool size. 

  • I updated my router to this version from the previous version, and so far there have been no issues

  • Kudos to NETGEAR for including a list of “known issues” in the firmware release notes – which has not been previously done, from firmware 1.0.0.48 through 1.0.11.94.

     

    P.S.: Publishing such a list was requested on the NETGEAR Idea Exchange in March, 2020 (see here).

    • mji71's avatar
      mji71
      Aspirant
      Two issues I am having with latest firmware:

      Minor: If you change the default Device Name of the router, the graphic image on the Advanced Setup > Wireless AP setting page is corrupt.

      Major: Once I configure as a Wireless AP, if the router suffers unexpected power loss, then the Web GUI no longer responds. I have to do a full reset. Happened multiple times already (ugh). The RAXE00 continues to function normally, but the Web GUI is non responsive and, also, ping fails.
    • Netgear usually publishes up date details when they go beyond "security updates".

       

      Like many software coders, it does not describe security updates for obvious reasons. To keep the criminals in the dark.

       

      Most firmware updates are purely security tweaks. Hence the lack of any details.

      • Killhippie's avatar
        Killhippie
        Prodigy

        Saying that its been almost 6 months sine the last update for the RAXE500, you think they would want to either get OOKLA speed test working on PPPoE and sort the 40Mhz issue out. The router is mature now so I guess these are not major updates for Netgear with all hands rushing to Wi-Fi 7

    • perseid's avatar
      perseid
      Aspirant

      I just updated the firmware and all seems fine, no issues.