NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
WAX210 random kernel crashes
I have three WAX210 and they all crash randomly every few weeks. I have the latest firmware version (1.1.0.36). I set up remote logging and here's the error (MAC address obfuscated): 2026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.021476] STA Addr 98:50:2e:xx:xx:xx Vlan ID 0 2026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.021484] Set_Sta_Vlan searching pEntry for Addr 98:50:2e:xx:xx:xx 2026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.021489] pEntry 00000000933180e0 found and set the vlan id to 0 2026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.021629] CFG80211_AuthRespHandler:ENTRY ALREADY EXIST, TERADOWN BLOCKACK SESSION 2026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.025412] 7981@C01L3,wifi_sys_conn_act() 1115: wdev idx = 0 2026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.025703] 7981@C08L3,hw_ctrl_flow_v2_connt_act() 215: wdev_idx=0 2026-09-27T19:16:35+00:00 ap3.home hostapd: ra0: STA 98:50:2e:xx:xx:xx IEEE 802.11: associated (aid 1) 2026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.027505] STA Addr 98:50:2e:xx:xx:xx Vlan ID 0 2026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.027513] Set_Sta_Vlan searching pEntry for Addr 98:50:2e:xx:xx:xx 2026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.027518] pEntry 00000000933180e0 found and set the vlan id to 0 2026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.028128] 80211> ifname=ra0 KeyAdd STA(98:50:2e:xx:xx:xx) ==>2026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.029132] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000037 2026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.029137] Mem abort info: 2026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.029139] ESR = 0x96000005 2026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.029142] EC = 0x25: DABT (current EL), IL = 32 bits2026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.029144] SET = 0, FnV = 0 2026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.029145] EA = 0, S1PTW = 0 2026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.029147] Data abort info: 2026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.029149] ISV = 0, ISS = 0x000000052026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.029150] CM = 0, WnR = 0 2026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.029154] user pgtable: 4k pages, 39-bit VAs, pgdp=0000000057434000 2026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.029156] [0000000000000037] pgd=0000000000000000, pud=0000000000000000 2026-09-27T19:16:35+00:00 ap3.home kernel: [1477020.029162] Internal error: Oops: 96000005 [#1] SMP I hope that can help fix the bug in a new firmware.WAX615 – Random reboot after ~72h uptime, matches known bug on latest firmware
Product: Netgear WAX615 Firmware version: V12.8.0.6 Summary: My WAX615 reboots unpredictably, roughly every ~71.9 hours of uptime (not a fixed wall-clock time), even with the scheduled reboot feature disabled. This matches the bug described in release notes for this firmware version — "Fixes the issue where the Access Point randomly reboots after associating with wireless clients" — but I'm still experiencing it on the latest firmware. Troubleshooting already performed: Scheduled reboot: disabled in web UI Cloud/Insight management: disabled, set to local (web-browser) management only WAN egress to Netgear cloud: blocked at the router (firewall rule) NTP: pointed at a local NTP server rather than Netgear/public NTP None of the above changed the reboot pattern Evidence from syslog (remote syslog enabled via web UI): Kernel drop_caches calls (unrelated housekeeping, occurs every ~8 min regardless) show an uptime counter that resets from ~258,830 seconds down to ~269 seconds, confirming a genuine reboot (not a logging gap) This ~258,800–259,200 second interval (≈71.9–72 hours) recurs consistently across multiple days of logs apmonitord "instantwifid not restarted | cloud_status = 0" messages recur every ~15 min continuously with no correlation to reboot timing No shutdown/reboot log entry appears before the gap; the AP simply stops logging mid-cycle and resumes with an NTP re-sync a few minutes later, consistent with a hard/watchdog reset rather than a clean reboot Request: Given the near-exact match to your documented bug fix, could you confirm whether this is a known residual issue on the current firmware, and whether a further fix is planned? Happy to provide the full syslog export if useful.WAX210 Band Steering Made AP hanging
I got a new WAX210 used in the office. Everytime I enabled band steering in the configuration, the AP hanged with red lights blinking. Then I can no longer login to AP unless factory reset. The AP has loaded the last firmware V1.1.0.36. Is it hardware issue or firmware issue? Does anyone have similar experience?NetGear WAX620 devices gets removed from Insight cloud frequently
Every other day, the Insight app pings me with: "The following device has been deleted from your network by (Me/Username)" . I am the sole administrator with access to the account, and I can confirm I am not orchestrating these deletions; I have every intention of keeping my job rather than speeding up my own professional demise. When this occurs, the access points drop from Insight-managed mode into standalone local mode (the power LED switches from blue to green). This is not isolated to a single unit—all 18 of our WAX620 APs experience this simultaneously. Had it been simple brownout or power loss, it should've said "Device Disconnected" but instead, it gets removed entirely from cloud which shouldn't happen automatically. Some Details: Power: All APs are powered via Rack PoE switch connected to a high-capacity inverter backup system, ruling out brownouts or power interruptions. There is also no power issues as all devices work normally on a good day Firmware: All units are updated to the latest firmware (v12.8.0.7). Networking: The issue persists regardless of whether DHCP or static IP addresses are assigned. Is this a known configuration issue, a bug within the Netgear Cloud backend, or something else entirely? Has anyone encountered a similar problem?AX600 missing Port Forwarding setting
I have an AX600 in router mode that has been running for multiple years with the same configuration and I had a port forward rule configured that was working on the initial setup. I am trying to edit the Port Forward rule but I am not seeing the setting/option anywhere in the management portal. I see everything that I normally see but am missing any Security and Firewall settings. What am I missing?WAX210 Firmware 1.1.0.34 Bug – SSID Password Complexity Incorrectly Enforced
Hi everyone — I’m seeing what looks like a firmware regression on the WAX210 after updating to v1.1.0.34, and I want to report it in case others are affected. After updating, the AP now refuses to save any configuration changes (even unrelated ones like just renaming the Access Point). The UI throws this error: SSID1: SSID passphrase length must be between 8 and 63 characters, and contain at least one uppercase letter, one lowercase letter, one number, and one special symbol. This happens even when the SSID password is not edited at all. The AP loads the existing (valid) WPA2/WPA3 passphrase and flags it as invalid due to a complexity requirement that didn’t exist before. This appears to be the AP Login Password complexity policy being mistakenly applied to SSID passphrases, which contradicts the official manual. SSID passwords for WPA2/WPA3 should only require 8–63 characters. Reproduction Steps Update WAX210 to firmware 1.1.0.34 Log into the web interface Make any change (example: AP Name only) Click Apply The SSID password complexity error appears, even though SSID settings were untouched Impact. The AP cannot accept any configuration changes unless the SSID password is replaced with a much more complex passphrase. This forces a complete re-key of all connected devices. Expected Behavior Per the WAX210 User Manual, SSID passphrases should be valid with: 8 to 63 characters No requirements for uppercase/lowercase/digits/symbols Those rules worked correctly in previous firmware versions. Current Workaround Rolling back to firmware 1.1.0.25 or 1.1.0.20 fully resolves the issue. Request Can Netgear please confirm whether this is a regression in 1.1.0.34 and escalate to the firmware engineering team? This issue effectively prevents configuration of the device. I can provide: Screenshots of the error dialog A configuration backup A short video showing the issue Exact hardware revision and serial if needed Thanks in advance.We have several WAX610Y that were added to device groups
We have several WAX610Y that were added to device groups. Everything runs right now on the new insight platform. Some of them were added and other failed and we had to re-add them manually on the insight using the serial number and MAC Address. Since then, we have several devices that constantly loose access to the insight (cloud). We have checked about DHCP exhaustion but did not find any issue on that side. Any thoughts on that issue ?Disable Auto Firmware Update - SXR50/SXS50
I have the SXR50 and 3 SXS50 satellites. The recent firmware update (V4.3.2.200) totally dorked up the routers. I would experience disconnects to wireless and hardwired devices were not picking up IPs correctly. I reverted back to the previous firmware version (V4.3.2.100) and all issues were resolved. However, the option to disable Auto Update for the firmware is greyed out. Any idea why this would be and how to allow me to disable it so I do not run in to this again?