NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
M4300 stack-port RX discarded packets, high mgmt latency
Hello, I have 4 M4300-28G-PoE+ (IP 192.168.101.4, fw version 12.0.19.23) in a stack ring, and one M4350-48G4XF (IP 192.168.101.5, fw 14.0.6.9), which is connected to the stack via 4 port LAG, each cord connected to one switch from the stack. The asic switching seems fine, I have <1ms latency on every device in the network, except for the stack management IP. Counters show RX discards on all but one stack cord (which is logically disconnected to prevent loop). The discards bleed steadily and more heavily if there are more devices in the network, though the data rate shows around 90Mb/s on each stack interface, which is nothing, when the stack interfaces show 10Gbit links. There are no errors, just RX discards (show stack-port counters all) as if the CPU buffer can't handle it. The stack management IP also has higher ping, 1-2ms with up to 80ms peaks. Those peaks are probably correlated with CPU usage spikes, normally sitting around 15 % on the Mgmt Sw, going well over 50% and even up to 80% (with agentMain, tRpcsrv.01000 and syncdb eating up the most at those peaks). There is VuWall AV system populating most of the switch ports. I have igmp-plus set up and igmpsnooping, with querier being the switch 192.168.101.4 (snoopTask eats almost nothing). The secondary switch 101.5 has set igmp mrouter 101 on the LAG and querier set to 101.4. Therefore IGMP should be correctly configured. I tried: Set all recommended settings for Netgear by VuWall. Upgraded FW from 12.0.19.21 to 12.0.19.23. Different presets in switch GUI. Disconnecting 3 out of 4 LAG ports. port-channel load-balance 3 and 6 and I have port-channel local-preference on that LAG, on both stack and M4350 I guess discarding rx packets on stack interfaces isn't a feature. Only the stack interface is having this high latency and sometimes our video streams freeze (this can be totally unrelated to the switch issue though) Disconnecting almost all devices, problems weren't as severe but persisted, which seems to me more like a broadcast storm/topology problem, rather than low bandwith problem. Any ideas of what could have been wrong?WAX615 – Random reboot after ~72h uptime, matches known bug on latest firmware
Product: Netgear WAX615 Firmware version: V12.8.0.6 Summary: My WAX615 reboots unpredictably, roughly every ~71.9 hours of uptime (not a fixed wall-clock time), even with the scheduled reboot feature disabled. This matches the bug described in release notes for this firmware version — "Fixes the issue where the Access Point randomly reboots after associating with wireless clients" — but I'm still experiencing it on the latest firmware. Troubleshooting already performed: Scheduled reboot: disabled in web UI Cloud/Insight management: disabled, set to local (web-browser) management only WAN egress to Netgear cloud: blocked at the router (firewall rule) NTP: pointed at a local NTP server rather than Netgear/public NTP None of the above changed the reboot pattern Evidence from syslog (remote syslog enabled via web UI): Kernel drop_caches calls (unrelated housekeeping, occurs every ~8 min regardless) show an uptime counter that resets from ~258,830 seconds down to ~269 seconds, confirming a genuine reboot (not a logging gap) This ~258,800–259,200 second interval (≈71.9–72 hours) recurs consistently across multiple days of logs apmonitord "instantwifid not restarted | cloud_status = 0" messages recur every ~15 min continuously with no correlation to reboot timing No shutdown/reboot log entry appears before the gap; the AP simply stops logging mid-cycle and resumes with an NTP re-sync a few minutes later, consistent with a hard/watchdog reset rather than a clean reboot Request: Given the near-exact match to your documented bug fix, could you confirm whether this is a known residual issue on the current firmware, and whether a further fix is planned? Happy to provide the full syslog export if useful.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?WAX638E Truncates MPSK Table
We have around 30 APs, about 24 of them WAX638Es, and the rest 620s, with one 610Y. We've deployed MPSK on a network, with 43 key entries. Currently, the full table copies to the 620s and 610Y, and users can instantly authenticate as expected. The 638Es, however, only copy in the first 8 entries, whether they are on PoE+, PoE++, regardless of switching config, and the issue persists after both an insight remove/re-add and a factory reset and re-add. I have an open case on this issue, started two days ago, but I wanted to post it here for posterity. JonahNetGear 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?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.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?
