NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
WAX220 firmware 1.0.3.5 apple instability
When I first bought my wax220 I had trouble with iPhones and iPads staying connected to 2.4g WiFi. Netgear produced firmware 1.0.3.4 and that solved the issue thankfully. I had no issues since. Yesterday I tried upgrading to firmware 1.0.3.5 and again my iPad had issues connecting. I could see in setting that the WiFi was constantly connecting disconnecting and reconnecting I downgraded the firmware and the issue was resolved. other devices such as Amazon fire tv seemed to connect ok but I didn’t stay on the new firmware for that long to really test ive seen other people complaining that 1.0.3.5 exhibits stability issues with apple devices any advice about this? Why hasn’t a new firmware been created? thanksFW page shows 'Updates Available'
Experiencing the same thing with WBE750 APs. Notification that FW updates are available went out and the FW page shows 'Updates Available' in some icons, but when you attempt to 'update' it just says you are on the latest version already (it's not). The manual files are not available on the downloads page either, so it's not possible to do it through the local interface. Forcing a factory reset and starting the device up from new also does not appear to make a difference (ask me how I know). Hoping this gets sorted out within a couple of daysNetgear WiFi 7 WBE710 802.11k/v Disabled After FW upgrade.
I upgraded to V11.8.0.14 and I'm not seeing on my devices that 802.11k/v are now disabled. I know 802.11r is only supported with InSights but now they are disabling features? I rolled back to V11.5.1.5 and then they show enabled. Why is Netgear disabling features for APs? Is anyone else seeing the same? You can't even open a support case with Netgear without paying nowadays. This are extremely useful protocols for device roaming and now they are disabled in the backend? I would like an explanation. Factory reset performed made no difference. Quick Configuration Settings - Everything else is default. Static LAN IP Configured 192.168.x.x SystemName Set LED Disabled - High doubt it is this. I've seen weirder Single SSID Configured WPA3/WPA2 Personal VLAN ID configured Band Steering Enabled Wireless Settings - 2.4/5/6Ghz All 3 bands are configured with Dynamic Channel WidthWAX210 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.
