NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
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?GS308EP sends management traffic outside configured Management VLAN
Hello, I would like to report a possible VLAN isolation issue with my GS308EP. Environment Device: NETGEAR GS308EP Firmware: V2.0.0.11 (latest as of writing) Configuration: The uplink port is configured as an IEEE 802.1Q trunk. Management VLAN is configured as VLAN 8. Management IP address is 192.168.8.18. The uplink is connected to a Linux router with multiple 802.1Q VLAN interfaces. The VLAN interfaces share the physical NIC's MAC address, which is the default behavior of Linux VLAN interfaces. The router also has arp_ignore=1 and arp_announce=2 configured to prevent ARP flux-related issues. Observed behavior Although the management VLAN is configured as VLAN 8, the GS308EP sends management-related traffic on VLANs other than VLAN 8. For example, packet captures show the switch sending ARP requests on multiple VLANs: VLAN 19: ARP Request: who-has 192.168.8.1 tell 192.168.8.18 Sender MAC: 28:94:01:XX:XX:XX The same ARP request appears to be sent on the VLANs configured on the GS308EP, in ascending VLAN ID order. In addition, management traffic generated by the switch, such as NTP, DNS, and UPnP/SSDP traffic, is observed on non-management VLANs. Expected behavior I would expect: - Management traffic generated by the GS308EP to be sent only through the configured Management VLAN. - ARP, NTP, DNS, UPnP/SSDP, and other management-plane traffic to use VLAN 8 only. - No traffic sourced from the management IP address (192.168.8.18) to appear on other VLANs. I can provide packet captures if needed. Thank you.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?GS116EP and Cisco Switch Trunk Issue
I need to pass multiple VLANS between a Cisco C9300 switch and a GS116EP. I've tried two brand new GS116EP switches, so it has to be an issue with the config. C9300 interface config: switchport trunk allowed vlan 1,10,20,30,40,50 switchport mode trunk switchport nonegotiate GS116EP config: port 1 is connected to the C9300 vlan 1 is untagged (C9300 native vlan ID) vlans 10,20,30,40,50 are tagged PVID is set to 1 The latest firmware version (2.0.0.5) has been installed. If I set corresponding C9300 interface to access mode, there's no issues. Trunking is the issue. What am I missing? Thank you for the help on this!Netgear Switch G5316v3
I setup a new home network and it worked for 3 mins then it stopped. Nighthawk MS80 system Modem connected to Mesh Router which is connected to Netgear G5316V3 16 port unmanaged switch which i then connected to CAble Matters 24 port Shielded RJ45 Patch Panel. Currently only have 7 confimed working ethernet lines to 2 TV's, Xbox, 2 PC's. 1 not used. When i set it all up and powered up, it all worked. Ethernet lines lasted about 5 mins then stopped. The error msg being shown is there is no internet signal. The wifi still works.However my ethernet cables no longer have internet signal. The Switch lights are all blinking and power is on. When i power cycle the switch the internet does not come back, however all the ports are blinking like its sending data. Is this Switch toast?AX600 missing Port Forwarding setting
I have an AX600 in router mode that has been running for multiple years with the same configuration and I had a port forward rule configured that was working on the initial setup. I am trying to edit the Port Forward rule but I am not seeing the setting/option anywhere in the management portal. I see everything that I normally see but am missing any Security and Firewall settings. What am I missing?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.GS305E Setup VLAN's from behind the switch
The PC used to configure the switch permanently resides downstream of the switch, on a VLAN, and MGMT VLAN that is not 1. It becomes a chicken & egg problem where you will be constantly locked out and forced to reset the switch as you try all the different combinations. I tried googling for solutions and the closest was the topic GS305E Trunking tagged and untagged VLAN's. It was very helpful. However my issue is slightly different and I wanted to share what worked. It was... a process. Step 1: Configure your upstream switch with a trunked port for all the VLAN's you intend to have traffic through the GS305E switch. In the case of a Ubiquiti EdgeSwitch 24 for example, it absolutely 100% requires a new trunked port... even though you already likely have a main trunk tagged and setup for VLAN's. Step 2: Manually configure your PC's IP address to be in the 192.168.0.x subnet. Plug your PC into any port on the switch. Which port you choose to plug into does not matter for initial configuration, they are all configured identically. Use a browser and go to 192.168.0.139 and login with the password: password. There is no username so this switch is not appropriate for a multi-admin environment. Step 3: Change your password. This is mandatory and you will be presented with a screen to do so immediately upon first successful login. Step 4: You will immediately see the main system settings page (home). Disable DHCP mode and provide the device with a static IP within the subnet range where it will permanently reside. Also provide the subnet gateway IP (Subnet DHCP server). Apply the changes, no reboot necessary, the browser will timeout because the switch will now be found at that new static IP. You will likely want to change your PC's IP again to be within the new subnet range. Step 5: Go to VLAN > 801.q > Advanced: and enable the advanced option. Step 6: Advanced > VLAN Configuration: add your VLANs. You cannot remove VLAN 1 it is hardcoded and also used as the management VLAN by default. DO NOT attempt to change the management VLAN yet if your management VLAN is not 1. You will do that at the very end almost as the last step. This is why a lot of people (meeeee) have locked up their GS305E during initial configuration by changing that too soon, don't do that, don't touch it, live with management VLAN as 1 until you have everything working. Step 7: Advanced > VLAN Membership: this is where you setup your trunked port and tags. Now is when you decide which port you want to be the trunk port. I use port 1 but port 5 is also a logical choice. Whatever port you decide to make the trunk the default VLAN 1 should be untagged and the rest of your VLAN's under it tagged. Step 8: Advanced > Port PVID: the trunk port should always remain as PVID 1. Change the PVID's to your VLAN ID's. A note of caution if you have a different management VLAN than 1. This will lock you out and force you to plug into a fall back port. If your management VLAN is 1 then you should be finished. Step 9: Advanced > VLAN Configuration: If you need to change your management VLAN now is the time, the last final step. If you would have attempted to change your management VLAN at any time during the prior processes you would have been locked out and likely forced to hardware reset the switch to defaults. This is what worked for me. I spent about a day trying to get it all to work and honestly I believe the one thing that prevented me from succeeding most of the time was not setting up that port as a trunk port on the Edgeswitch. It shouldn't be needed like that but it definitely does not work if that trunk checkbox isn't checked. All feedback, corrections, comments, will be gladly accepted. Just please try to keep them constructive.
