NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Old ReadyNAS 212 won't boot up
So, many, MANY, years ago, my workplace merged with another company, and as part of that merger, I took over their IT system, which consisted of a few peer-to-peer PCs and a central storage system consisting of two ReadyNAS devices, one primary and one backup. Some time later, the backup NAS failed. Rather than fix or replace it, I opted to move to a cloud storage backup system instead, and the old unit was shelved. Fast forward to the modern day, amid a bunch of other IT problems cropping up (mainly, the current state of Microsoft OneDrive causing a cascade of problems with the cloud backup), the question of the the longevity of our current NAS device was raised. By my best estimation, that NAS has been going strong for upwards of 11 years now, and while it's performance has been incredible, it's at a point where it could fail at any moment. As part of the disaster recovery planning, the decision was made to try to refurbish the old backup NAS, just in case an immediate replacement is necessary before a full replacement can be purchased and implmented. That brings me to my current issue. The old NAS is able to power up, but then all the lights go out and it doesn't load anything. I have probed the Hard Drives on my PC, and while I haven't been able to access the files directly, the disks themselves seem to be fully functional. Most worryingly, attempting to access the Boot Menu with the reset button has failed entirely. Any advice of how I can get this old thing functional again? Preserving the data doesn't matter, they're just outdated backups, I just need to get the NAS Enclosure itself functional and active.SXR30
Hello, Use a Orbi SXR30 with 4 satellites for my home network. Previous to recent Insight update (4.3.4.300) phone app listed all connected devices and allowed blocking access through the app. Now when clicking "connected devices" the app shows "no connected clients available". On the "about" tab of the app, it shows 38 connected clients. Thanks for any assistanceWAX610 cannot be added to Insight - ownership release required
Hello, I have a NETGEAR WAX610 that I cannot add to Insight. Error message: "This device was previously added to a different account." I have already factory reset the device multiple times. Serial number: 6KE10C280023E I understand this device was previously used at another location and I do not have access to the original account. Could you please assist with ownership release so I can use the device with Insight? Thank you.WAX210 iPhone WPA3 Incorrect Password isBSSIDDenylisted 1
Hi I've been using a WAX210 as my home access point for a few months and every few days my iPhone is banned from the network. It won't auto-connect and if I manually connect it fails with "Incorrect password" I enabled iOS Wi-Fi diagnostics and it shows the BSSID has been banned for connections, with isBSSIDDenylisted 1. WAX210 running latest Firmware V1.1.0.34 released 25th July 2025 iPhone 16 Pro running latest iOS 26.3.1 5Ghz network WPA3 password I have also submitted feedback to apple as FB22209711 in case it is their bug. I believe it's either a bug in the WAX210 that is getting it banned by the iPhone or the iPhone's banning logic is too restrictive. Relevant log lines below: 03/12/2026 9:02:39.181 __WiFiDeviceManagerKnownNetworkSuitabilityCheck: Network 'agate', isFilteringAJCandidates 0, isSSIDTemporarilyDenylisted 0, isBSSIDDenylisted 1, isTDDenylisted 0 03/12/2026 9:02:39.181 __WiFiDeviceManagerKnownNetworkSuitabilityCheck: Not considering problematic Network agate isSSIDTemporarilyDenylisted 0 isBSSIDDenylisted 1 isFilteringAJCandidates 0 isTDDenylisted 0GS110EMX: 10G ports throttle uploads to 250-300 Mbps
I've been going back and forth with Netgear support for over a week about this and I'm honestly at a loss. I'm hoping someone here can tell me if I'm crazy or if what they're telling me doesn't make sense, because it really doesn't add up to me. My Setup Switch: Netgear GS110EMX (firmware 1.0.2.8) Port 1: Internet uplink (1G, connected to router — standard fiber ISP) Port 9: Mac Pro via OWC Thunderbolt 4 to 10G Ethernet Adapter Port 10: Asustor AS6508T NAS (10G) Cables: Cat6A throughout This is exactly why I bought this switch — two 10G ports for my computer and NAS, with everything else on the 1G ports. Pretty standard home prosumer setup. The Problem Internet uploads are throttled to about 250-300 Mbps when my computer is on a 10G port. Downloads are fine at 830-880 Mbps. When I move the same computer to a 1G port with the exact same cable, uploads jump to 708 Mbps. That's more than double the speed on a port that's supposedly 10x slower. What I've Tested (at Netgear's request) I ran every test their L3 support team asked for. Here are the results: Internet Speed Tests (computer on 10G port 9): Flow Control Download Upload OFF 865 Mbps 306 Mbps ON (port 9 only) 879 Mbps 169 Mbps ON (both 9 & 10) 820 Mbps 137 Mbps Internet Speed Test — computer on 1G port (same cable, same everything): Download Upload 884 Mbps 708 Mbps iPerf3 between Mac and NAS (local, 10G ↔ 10G): Direction Speed Mac → NAS 3.73 Gbps NAS → Mac 9.40 Gbps Local 10G performance is excellent. The ports, cables, and NIC all work fine. What Netgear Says After all this testing, support came back and told me: This is "working as expected" and "within the design limitations of the switch" The 10G ports are "intended to be used as uplinks" — not for client devices A replacement would behave the same way My configuration is "not the intended use case" Why I'm Confused I don't understand how any of this is "expected behavior." Specifically: How does a 1G port give me faster uploads than a 10G port? If the 1G uplink is the bottleneck, moving to a slower port should give me equal or worse speeds. Not more than double. Nobody has explained this. Why are only uploads affected? Downloads through the 10G port hit 865 Mbps — nearly saturating the 1G uplink. The traffic crosses the same 10G/1G speed boundary in both directions. Why would only one direction have "buffer overflow" problems? Flow Control made things WORSE. They asked me to enable it. It dropped uploads from 306 Mbps to 137 Mbps. How is that a fix? The product page says "No Network Bottlenecks thanks to the 2 10-Gigabit/Multi-Gigabit Uplinks." Now support says those ports are only meant to be uplinks and my setup is unsupported. The user manual literally shows 10G client devices connected to ports 9 and 10 in its network diagrams. This switch used to work. I used the exact same setup with fiber in Chicago for years with no issues. I only noticed the problem after switching to fiber here in LA recently. Something changed. What I'm Asking Has anyone else seen this? Am I wrong to think a managed switch should be able to handle 10G devices sending traffic through a 1G uplink without losing 70% of the uplink's capacity? I've seen a couple other threads about similar issues with the GS110EMX and I'm starting to think this is a known design flaw that Netgear just doesn't want to acknowledge. At this point I just want to know if I should keep fighting for a replacement or just give up and buy a different switch. Any insight would be really appreciated. I've spent way too many hours on this already.WAX630 continuous reboot loop: dvlan_fallback=1 firmware bug (hostapd_tr SIGABRT)
Hardware: WAX630, firmware 12.5.0.15, managed via Netgear Insight My WAX630 has been crashing and rebooting every 15–20 minutes for months, and after digging through the AP's own diagnostic logs I've pinpointed the root cause. Sharing here in case anyone else hits this and hoping someone has found a workaround I haven't tried yet. What's happening After every reboot, the crash repeats on the same ~17-minute cycle: hostapd_tr crashes with SIGABRT (signal 6) → configd loses IPC connection → nddmp database timeouts → apmonitord watchdog fires ("confd_stuck_handler: No response from configd") → AP reboots → repeat The AP's own `/etc/sysconfiglog/log/` directory has three `core.hostapd_tr.*.tar` crash dumps spanning March 2025 through July 2025, all with the same signal-6 signature, so this has been happening across multiple firmware versions (V10.8.12.9 and V10.8.13.2, and now current 12.5.0.15). Root cause (from the logs) The firmware config generator is writing `dvlan_fallback=1` on every VAP even though Dynamic VLAN (`dvlan_status`) is `0` (disabled) on every SSID. That contradiction means hostapd tries to open an L2 packet interface on the VLAN bridge (`br-lan`) for each VAP on every boot, and fails. Every boot produces 193 occurrences of this error in `hostapd.txt`: Failed to open l2_packet interface for vlan bridge Those failures flood hostapd_tr until it hits an unrecoverable state and aborts. The fix is straightforward: set `dvlan_fallback=0` on all VAPs. But `dvlan_fallback` isn't exposed anywhere in the Insight UI, and SSH is locked to Netgear engineering on Insight-managed APs, so there's no way for an end user to push that change directly. Proof it's WAX630-specific, not a config issue I compared against a WAX610Y at the same Insight location receiving the identical config push: WAX630 WAX610Y `dvlan_fallback` value 1 1 - identical `dvlan_status` value 0 0 - identical l2_packet errors per boot 193 0 hostapd_tr core dumps 3 confirmed 0 Crash frequency Every ~17 min Never Continuous uptime ~14 min 5h 41 min Same Insight account, same location, same SSIDs, same config, zero errors on the WAX610Y, constant crashes on the WAX630. This is a WAX630-specific hostapd behavior, not a network or config mistake on my end from what I can tell. What I've already tried (all failed to fix dvlan_fallback) Toggling VLAN IDs (1 → 2 → 1) on all SSIDs via Insight Enabling WPA2 Enterprise + Dynamic VLAN on a test SSID, then disabling `dvlan_fallback` still written as `1` SSH resets at KEXINIT, confirmed blocked for end users on Insight-managed APs Factory reset + re-adoption, reset firmware on the device to pick up net-new configuration from Insight, but since `dvlan_fallback=1` is written by the config generator on every Insight push, it reproduces the same config Temporary stability workaround (not a fix) I stabilized the AP by removing the secondary crash trigger: a client device was connecting at -88 dBm RSSI in a rapid 802.11r roaming loop, creating additional hostapd churn on top of the dvlan_fallback stress. Changes applied via Insight: Disabled 802.11r (Fast Roaming) location-wide Enabled Load Balancing → Balance on Client Rx RSSI (value 23 ≈ -72 dBm threshold) Enabled Disassociate Sticky Clients (2.4GHz: -70 dBm, 5GHz: -80 dBm, 6GHz: -78 dBm) After these changes: 12+ hours continuous uptime, zero l2_packet errors on current boot. But `dvlan_fallback=1` is still in the config; this is a bandage, not a fix. If hostapd stress increases for any reason, the underlying bug will reassert. Netgear's own 12.5.0.15 release notes list "Hostapd interface wifixvapx is unresponsive" as a known open issue. This appears to be the specific config path (dvlan_fallback=1 + dvlan_status=0) that triggers it. What I'm looking for Has anyone found a way to force `dvlan_fallback=0` through the Insight UI (or any other end-user-accessible method)? Has anyone had Netgear support successfully push a remote config fix for this? Is anyone else seeing this same crash pattern on WAX630? Would be helpful to know if this is widespread. I have detailed logs including three device-generated core dumps and before/after comparisons if anyone from Netgear engineering wants to look. Happy to share. Firmware: 12.5.0.15 | Management: Insight | Crash signal: SIGABRT (6) | Affected process: hostapd_trGS752TPV3 "comcast uplink port"
Howdy All, We have instrumented our first "new to us" Netgear switch for our classroom (to replace like 7 smaller switched that were scattered around) and I got it up and running, but realize that PORT 7 is the "uplink to our comcast router" port and now we're putting a new classroom computer onto that port, so I need to move the uplink line. I tried changing the VLAN to include Port 48 and Port 39 (both free in our schema) and moved the network line, but the switch refused to route traffic. I rebooted the switch (not reset, restart) to see if "coming up on the new line" would work, but no. If I move the line back to port 7 (still in the VLAN) it resumes functionality. I have checked the port configurations in the switch web admin, and they are identical. I have checked the VLAN membership configuration, and all three ports are "U"ntagged, with the same attributes. Any ideas? Thanks in advanceNighthawk M2 IP PassThrough stops working when idle
So I have a Nighthawk M2 in IP PassThrough with a VPN tunnel uplink over time it disconnects from 4G network for some reason and as soon as I login to the Nighthawk it springs to life. firmware NTG24_10.19.03.00 So anyone else having this problem? the ISP is o2