NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
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.M4300-52G-POE+ Bricked Recovery Method
Anyone knows how to recover from a power outage that bricked my M4300 ? M4300-52G-POE+ We had an outage. Power came back on, then the unit boots but none of the 52-ports came back up. The OOB port lights up when plugged into, but nothing. Then I console it and got the readout. It didn't even get past port0 and stalled out. Here is the vid: https://www.youtube.com/shorts/7Q5zGWaNzxY About 8 seconds into it and the screen will show upWAX610 – 802.1X Supplicant on Wired Uplink Port – Feature Availability
Hello NETGEAR Support Team, I am currently deploying a network infrastructure using several WAX610/WAX620 access points (firmware up to date) combined with a MS510TXPP managed switch. As part of my security architecture, I would like to enable 802.1X port authentication on the switch ports connected to the access points, in order to prevent unauthorized access in the event an AP is physically removed and replaced by a rogue device. This requires the WAX610 to act as an 802.1X supplicant on its wired uplink/LAN port — independently from the 802.1X authenticator role it already plays for wireless clients via RADIUS. After reviewing the WAX610 user manual thoroughly, I could not find any mention of this capability on the wired port. My questions are: Does the WAX610 currently support 802.1X supplicant functionality on its wired uplink port? If not, is this feature on the roadmap for a future firmware release? This is a fairly standard enterprise security requirement, and I believe many customers deploying WAX610 in environments where physical security of the AP cannot be fully guaranteed would benefit from it. Thank you for your time and assistance. Best regardsGS728TP v1 failed update
Can you tell me if it's possible to restore the GS728TP v1 after a failed update? The firmware was 6.0.1.14. I updated to the latest firmware 6.0.1.30 via SCC (Smart Control Center). SCC (Smart Control Center) reported that the firmware was updated and the switch would reboot. But after this update, the switch keeps rebooting. How can I restore it?Nighthawk M2 IP PassThrough stops working when idle
So I have a Nighthawk M2 in IP PassThrough with a VPN tunnel uplink over time it disconnects from 4G network for some reason and as soon as I login to the Nighthawk it springs to life. firmware NTG24_10.19.03.00 So anyone else having this problem? the ISP is o2WAX630E v12.8.0.6 log messages
I’m hoping someone from Netgear support can pass this along to engineering. Since updating my multiple WAX630E access points to firmware version V12.8.0.6, all of them are continuously displaying the following messages in the system log files. New messages are generated about every second. May 3 09:26:44 nddmp[5641]: nddmp total time to execute = 1.000000 seconds May 3 09:26:43 nddmp[5641]: NDDMP: data received from lighttpd = "[REMOVED]" May 3 09:26:43 nddmp[5641]: nddmp total time to execute = 0.000000 seconds May 3 09:26:43 nddmp[5641]: NDDMP: data received from lighttpd = "[REMOVED]" May 3 09:26:43 nddmp[5641]: nddmp total time to execute = 1.000000 seconds May 3 09:26:42 nddmp[5641]: NDDMP: data received from lighttpd = "[REMOVED]" May 3 09:26:30 root: monitor_stuck is running May 3 09:26:14 root: monitor_stuck is running May 3 09:25:58 root: monitor_stuck is running May 3 09:25:42 root: monitor_stuck is runningWAX210 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 0