NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
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_trWAX210 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 0Orbi Pro Router (SXR80) Satellite Connection Issues (SXS80)
I have been running two networks based on the SXR80 router and SXS80 satellites. Recently I have been seeing a strange behavior. The Insight App and Cloud say the satellites are NOT connected, but the Satellites show Blue LED indicators which suggest they are connected. I have done complete restarts of the system from the cable modems, then router then satellites, but nothing gets the insight app to see them as connected? I also noticed a very strange behavior in the insight cloud portal as well. connections to the network that are listed as "Wired" are all wireless devices?!? I have no idea why that would display in that fashion when thinks like wireless cameras, mobile phones and ring doorbells are clearly not wired to the network. Is this a firmware issues? Any suggestions? Thanks!Netgear WiFi 7 WBE710 802.11k/v Disabled After FW upgrade.
I upgraded to V11.8.0.14 and I'm not seeing on my devices that 802.11k/v are now disabled. I know 802.11r is only supported with InSights but now they are disabling features? I rolled back to V11.5.1.5 and then they show enabled. Why is Netgear disabling features for APs? Is anyone else seeing the same? You can't even open a support case with Netgear without paying nowadays. This are extremely useful protocols for device roaming and now they are disabled in the backend? I would like an explanation. Factory reset performed made no difference. Quick Configuration Settings - Everything else is default. Static LAN IP Configured 192.168.x.x SystemName Set LED Disabled - High doubt it is this. I've seen weirder Single SSID Configured WPA3/WPA2 Personal VLAN ID configured Band Steering Enabled Wireless Settings - 2.4/5/6Ghz All 3 bands are configured with Dynamic Channel WidthWAX204 cannot run on UPS
I have a WAX204 which I need to plug into a UPS. It runs okay if the UPS is plugged into AC power. However, whenever the power goes out, the router reboots and gets stuck in a boot loop. The loop happens whenever it is about to turn on the WiFi light, then it reboots back to the red light and repeats all over. However, once the AC power is restored to the UPS, everything is back to normal. I had thought it was the UPS power, and I bought a 2000VA / 1200W power supply, which is the same. How can I use this router on UPS? Here is the exact UPS: https://www.hikvision.com/africa/products/premises-distribution-system/ups/back-up-type-ups/ds-ups2000/Netgear WiFi 7 WBE710 Crashing/Rebooting
I have 3 WBE710 APs that I am not using InSights on only using local GUI. Last week I decided to update them from V11.5.1.5 to V11.8.0.14 and since then 1 AP has been having a Reboot reason code of "Crash". The other 2 APs are stable and have been up and online since the upgrade. All 3 APs are configured in the same settings minus two APs are configured to have the LEDs off. One of the APs that is configured to the LEDs off started crashing every 3-12 hours. I did a typical restore to defaults and reconfigured to match the other settings of the APs and the single unit continued to crash. As a quick test I downgraded the crashing unit back to V11.5.1.5 "downgrading forces factory reset", reconfigured again to match the exact settings of the other APs, minus the LED setting. Since then it has been stable. Quick Configuration Settings - Everything else is default. Static LAN IP Configured 192.168.x.x SystemName Set LED Disabled - High doubt it is this. I've seen weirder Single SSID Configured WPA3/WPA2 Personal VLAN ID configured Band Steering Enabled Wireless Settings - 2.4/5/6Ghz All 3 bands are configured with Dynamic Channel Width Any thoughts would be welcomed. I don't really want to leave them on mismatch FW.Second hand wax630 keeps restoring to insight
I have 4 second hand wax630 that are unable to restore to factory defaults When I restore them to factory default I am able to access the web page one time and when I try a manual setup it reboots and restores the previous owner insight settings. Tried this multiple times and was able to do a firmware upgrade on it, but after a while it keeps restoring to the previous owners insight setting Offcourse I have no access to this account, I have aquired them legally offcourse but find it strange that if someone locks them nobody can access them. I guess when an it manager leaves a company the company is pretty much screwed (or when the it support firm goes out off bussiness) Anyone a solution for thisWAX210 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.wax202 no ethernet connection
Hello, I have a wax202(AX1800) I was using as an access point then decided to move it to main router function so I did a reset. I don't know if its related but now I have no ethernet connection(no orange or green light and no internet connection to pc or laptop) My old netgear router has a working throughput for ethernet when connected so it's not an isp or cable issue. tried a pushbutton reset a few times no luck, is my 202 dead? Is there a way to push a firmware update without an internet connection? ty
