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.Poor Quality Video MS Teams/Zoom
Hi there, I have installed an Orbi RBK852 last week and had some significant issues with zoom and teams. Over a period of 6 days, I have spoken/called Telstra (ISP) and Netgear multiple times with little to no answers or improvements. My Orbi RBK852 is connected directly into a NBN CO NTD FTTC box which has replaced the Telstra CobraAX Gen 3 Modem. The Orbi connected perfectly and picked up everything automatically from the ISP and was ready to go. Download speed 102/upload 19. When trying to use zoom and teams, the packet loss and sent bitrate is incredibly low and poor. After ticking disable SIP ALG, Nat Filtering set to Open and unchecking disable IGMP Proxying I was able to have zoom to return to no freezing and stutter with only 1% packet loss and not up to 90% packet loss. However, MS Teams is still running like I am frozen in time. The changes I listed above improved my sent bit rate from 0.2 to 1.1 mbps but not enough to have a solid video for the person on the other end. When they watch me on their mobile or when I share screen, the video is fine (I think because of the low resolution/screen size). But normal size impairs the teams completely. I use MS Teams and Zoom up to 55 hours a week and work from home so this is incredibly distressing. I do not want to accept defeat and set the RBR to AP mode, I want this to work as a router and modem. I have tried playing with other settings, the CTS/RTS was increased from 1, to 500, 1500 and 2347 (max) with no change. I set the radio frequencies to auto and 48 (even though the issue still occurs when plugged directly into the RBR. NG support did a ping test no issue. They did it to zoom/teams and there is a timed out request but that issue exists even when I do not use the Orbi system, the ISP and NBN have the same time out but when I plug the ISP modem back in and connect to that, absolutely no issue with teams or zoom. I have tried this in browser and app (updated both and I am up to the latest firmwire on the router and satellite). I would love any ideas or anything I can change to try increase its performance. It seems that the Orbi system does not want to allow the traffic to these services but I am also not the most technologically advanced and would love any assistance. Someone out there must have had the same issue and can explain it in a way that doesn't make numbers/equations fly across my vision. I have my ISP arguing that it is the Orbi system, I have NG argue that it is the NBN/ISP. Like most of us, I spent a lot purely to get 40 + devices connected and future proof because the ISP modem would drop connections and devices constantly sitting at 20 devices. Please help! AX6000 WiFi Mesh System (RBK852)MS510TXM - Private VLAN Promiscuous Port Issue
Hello, I am following the directions on how to properly setup a promiscuous port on a private vlan that allows communication between the two associated community ports. I am unable to add more than one secondary vlan in the interface and the manual clearly says it's possible so I must be missing some nuance. VLAN Type Configuration 20 - Primary 21 - Community 22 - Community Private VLAN Association Primary 20 --- Secondary 21-22 --- Community 21-22 Port Mode Configuration I8 - Promiscuous (LAG) Private VLAN Promiscuous Interface Configuration Here is page 180 of the manual under: Private VLAN promiscuous interface: Assign the interface to primary and secondary VLANs ... ... 9. In the Promiscuous Primary VLAN field, specify a primary VLAN ID. You can select a VLAN for which you configured the type as Primary (see Assign a private VLAN type to a VLANonpage171). 10. In the Promiscuous Secondary VLAN field, specify one or more secondary VLAN IDs. You can specify VLANs for which you configured the type as Isolated or Community, both of which are secondary VLAN types within a private VLAN. You can specify a single VLAN ID, a range of VLAN IDs, or a combination of both in sequence separated by a comma (,): You can specify an individual VLAN ID, such as 10. You can specify the VLAN range values separated by a hyphen, for example, 10-13. • You can specify a combination of both separated by commas, for example: 12,15,40–43,1000–1005, 2000. ERROR Error: Value (0) is out of range for 'Promiscuous Secondary VLAN'. The valid range is 2 to 4095. I have tried to add 2 secondary vlans with the comma approach 21,22 and with the hyphen approach and both give the same error. The Secondary VLAN field only accepts 1 vlan so how do you configure a promiscuous port in a private vlan?WAC720 bricked
We have a few WAC720 AP's controlled by a WC7500 Wireless controller. So far I have: Performed a hard reset to the AP (holding button down for 10/15seconds) I can only use Putty to conect to the AP via the console port. The state of the AP LED's: power - solid green activity - no light network/lan: no light Thoughts, has anyone found a work arround for this AP? Thanks :)Discovery Tool - no network options in drop down
I am trying to use the NETGEAR Discovery Tool on a relatively fresh installation of Windows 11 Pro. I have confirmed that sharing and network discovery are enabled on the computer, but don't know where else to look. I have another identical computer on our network with the same settings and it works as intended. I spoke with support and they told me to check my services, but they all are running. Any help would be appreciated!Home Account should be Business
Does anybody know how to contact Netgear when you have an admin problem (not tech support). For several years I have emailed different people (sales, support etc) asking why my account is setup as a Home account when it should be a Business Account. I never get a reply. That means that every invoice that I get from Netgear Ireland has VAT on it which I cannot reclaim because it is an Irish VAT number. It should be dealt with under the reverse charge procedure and have no VAT added. So far I cannot find and point of contact to deal with mundane issues such as this but it is costing me money every time I have to renew a support contract and it stops me buying anything direct from Netgear. I am about to spend a few thousand pounds on new Wireless Access Points and I'm seriously thinking of using a different product. Thanks for any help.WAX615 Mehrere APs als quasi Mesh nutzen
Hallo Zusammen, ich habe zwei WAX615 APs und möchte dies noch um einen dritten evtl. sogar vierten erweitern um bspw. die verschiedenen Ebenen/Bereiche einer Immobilie abzudecken: AP1 = Paterre AP2 = Garage AP3 = Garten AP4 = 1. Stock Genutzt werden drei verschiedene SSIDs und Einstellungen: SSID mit nur 5GHz Sendekanal für AP1 40/5,2 GHz Sendekanal für AP2 48/5,24GHz PMF 802.11w optional Band Steering / 802.11 k/v aktiviert SSID mit nur 2,4GHz (Auto Kanal einstellung) PMF 802.11w optional Band Steering / 802.11 k/v aktiviert Gast-SSID mit beiden Frequenzen PMF 802.11w optional Band Steering / 802.11 k/v deaktiviert Allgemein Einstellungen: QoS ist für alle Frequenzen mit WMM und WMM Powersave aktiviert Spannung Tree Protocol aktiviert Network Integrity Check aktiviert IGMP Snooping deaktiviert Ethernet LLDP aktiviert UPnP aktiviert Powersetting 802.3at Load Balancing aktiviert Force Sticky Client ti disassociate deaktiviert Leider war die Anleitung da für mich nicht sehr hilfreich, daher wäre meine Frage: Was wäre die optimalen Einstellungen um die selben SSIDs auf allen APs quasi wie ein Mesh zu benutzen ohne die Insight App zu nutzen und Lokal zu konfigurieren? Viele Grüße und ein schönes verlängertes WochenendeAuto Voice VLAN setup
We are looking to isolate our VoIP traffic to its own VLAN. For a number of reasons, we'd like this to happen without needing to configure each phone. It looks like Netgear switches support this. Unfortunately, the documentation is scattered and in many cases outdated. I'm hoping some folks here can show me where we're going wrong. Goals: Voice VLAN = 88. Ports 1-44 set to untagged VLAN 1 and VLAN 88. Default to 1 unless MAC address prefix matches a VoIP device. Ports 45-46 are for router for Voice-VLAN and has no access to VLAN 1. Ports 47-48 are for router normal VLAN (1) and has no access to VLAN 88. Ports 49-52 are uplinks and should carry traffic for both VLANs. The phone should be able to operate in pass-through mode, and devices behind them should default to VLAN 1 as they normally would. Currently I am facing two issues: When I plug in a phone with matching MAC prefix, it is not being pushed to VLAN 88. I'm unable to outright disable Voice-VLAN (88) on ports 47-48. I'll add some screenshots of the current config in a follow-up post. Hopefully some kind network admin will take a look and be able to spot where I'm going wrong.
