NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Firmware
3 TopicsWAX220 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? thanksWAX210 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.338Views3likes0CommentsWAC104 dropping connections disassociated deauthenticated and DHCP issues (possibly solved)
Sorry for a long post, and if this issue has been raised and answered. But I've had wireless connection issues on a WAC104, and believe I found the cause. I have somewhat complex home network which includes a server, two netgear managed switches, an AT&T 2-Wire residential gateway, and a WAC104 access point. I have been experincing issues with dropped wireless connections, failures to connect, WAC104 logs showing frequent entries for "disassociated", "deauthenticated", and "WLAN access rejected: incorrect security". The WAC104 "Attached Devices" would only list a single device when we have multiple wireless devices. I believe the issue was caused by my using a static IP address for the WAC104. Given the complexity of my network I prefer to use static IP adresses for certain devices, my server, switches, printers, televisions, and the WAC104. But all other devices were DHCP assigned from a range established on the 2-Wire gateway. We have been expreiencing frequent disconnects of wifi devices, and failures to reconnect. I enabled debugging on some android devices, and found log entries with "NETWORK_SELECTION_DISABLED_DHCP_FAILURE" It seems that by having the WAC104 configured with a static IP address it was breaking DHCP assignments for devices that were connecting through it. I reconfigured the WAC104 to use DHCP for its own address and immediately saw an improvement. The UI on the WAC104 now shows all connected wireless devices and so far, (2 hours time passed), no connections have dropped. I would not have expected that the use of a static address for the WAC104 would have prevented the wireless clients from using DHCP from the 2-Wire gateway. But this seems to be the case.2.5KViews0likes5Comments