NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
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?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.WAX610Y and WAC540 Bridged Network
I have a WAC540 that is working great, and it's connected hardwired. There's a driveway gate controller that needs internet access, but no hardwired network available. So, I purchased a WAX610Y (since it's used outdoors), made the WAC540 the root, and WAX610Y the extender. I also used a PoE injector to power the WAX610Y. The WAX610Y also services outdoor clients. Both connect and formed a bridge across a long driveway. Although it's only 50 feet away, the wireless strength reported "good" (one below "excellent") at -54 dBm. I connected a laptop to the other end of the CAT5e that is connected to this WAX610Y, and I was getting very poor internet speed, something like 5-10 mbps up/down where it's normally 600+ mbps. I reset everything, did firmware upgrade, etc., but I am still having connectivity issues. It's also disconnecting and reconnecting every so often. Can you tell me if the WAX610Y supports extending the network across the driveway? This is how I have it: Gate Keypad <-CAT5e-> PoE Injector <-CAT5e+PoE-> WAX610Y <-wireless-> WAC540 WAC540 <-> router <-> internet Thanks for any advise for getting this to work properly.WAX210 iPhone WPA3 Incorrect Password isBSSIDDenylisted 1
Hi I've been using a WAX210 as my home access point for a few months and every few days my iPhone is banned from the network. It won't auto-connect and if I manually connect it fails with "Incorrect password" I enabled iOS Wi-Fi diagnostics and it shows the BSSID has been banned for connections, with isBSSIDDenylisted 1. WAX210 running latest Firmware V1.1.0.34 released 25th July 2025 iPhone 16 Pro running latest iOS 26.3.1 5Ghz network WPA3 password I have also submitted feedback to apple as FB22209711 in case it is their bug. I believe it's either a bug in the WAX210 that is getting it banned by the iPhone or the iPhone's banning logic is too restrictive. Relevant log lines below: 03/12/2026 9:02:39.181 __WiFiDeviceManagerKnownNetworkSuitabilityCheck: Network 'agate', isFilteringAJCandidates 0, isSSIDTemporarilyDenylisted 0, isBSSIDDenylisted 1, isTDDenylisted 0 03/12/2026 9:02:39.181 __WiFiDeviceManagerKnownNetworkSuitabilityCheck: Not considering problematic Network agate isSSIDTemporarilyDenylisted 0 isBSSIDDenylisted 1 isFilteringAJCandidates 0 isTDDenylisted 0IOS Apple Devices Dropping
I have WAX625, WAX610, & 605. For a number of months now, my IOS devices continue to drop their WIFI and then takes 2-5min to reconnect. I originally had Load Balance and Remove Sticky Clients configured. I have put everything back. Firmware on the AP is 10.8.13.2 I am a technical guy and I feel I have tried all the other things that have been mentioned in posts that sort of sound like mine. I think this is only happening on my 5/6ghz SSID. I Have a SSID for 2.4 and one for 5/6. Any suggestions? Anyone else seeing this? Im so frustrated that I'm looking at a different vendor for the house. I am managing these in Insight.