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 0PR60X Adguard login
Hello Sirs, Long time no see which means everything works fine except lack of IPV6 still. ( but its not important right now ) But could it be possible in the next firmwire update to add username/login for adguard DOH ? I, for exemple use https://adguard-dns.io which looks like https://d.adguard-dns.com/dns-query/XXXXX Right now I must use it on a adguard home lan server to able to do so and put it as dns for the lan using 192.168.1.X adresss in the PR60X configuration. Being able to put an argument in the adguard pr60X configuration would allow me to get rid of it. Thank you for your feedback.FW page shows 'Updates Available'
Experiencing the same thing with WBE750 APs. Notification that FW updates are available went out and the FW page shows 'Updates Available' in some icons, but when you attempt to 'update' it just says you are on the latest version already (it's not). The manual files are not available on the downloads page either, so it's not possible to do it through the local interface. Forcing a factory reset and starting the device up from new also does not appear to make a difference (ask me how I know). Hoping this gets sorted out within a couple of daysWAX220 firmware 1.0.3.5 apple instability
When I first bought my wax220 I had trouble with iPhones and iPads staying connected to 2.4g WiFi. Netgear produced firmware 1.0.3.4 and that solved the issue thankfully. I had no issues since. Yesterday I tried upgrading to firmware 1.0.3.5 and again my iPad had issues connecting. I could see in setting that the WiFi was constantly connecting disconnecting and reconnecting I downgraded the firmware and the issue was resolved. other devices such as Amazon fire tv seemed to connect ok but I didn’t stay on the new firmware for that long to really test ive seen other people complaining that 1.0.3.5 exhibits stability issues with apple devices any advice about this? Why hasn’t a new firmware been created? thanksGS752TP Firmware Upgrade Failed
I attempted to upgrade a GS752TP from firmware version 60.0.1.16 to 60.0.1.30. I followed the instructions here, just with the 60.0.1.30 firmware instead of .24 as shown in the instructions. When I rebooted, the switch powered up, but I cannot connect to it in any way. The Power LED lights up and alternately switches between green and orange very slowly (maybe once a minute). The LED Mode LED is on solid green. When the Power LED is orange, the port 37 and 43 link LEDs light up solid regardless of if anything is plugged in. When the Power LED is green, whatever ports I plug into will light up solid orange. The LED Mode LED stays on solid green the whole time. I've tried pushing the "Reset" and "Factory Default" buttons on the front and they don't seem to do anything (i.e. - it doesn't reboot/reset as far as I can tell). I've tried connecting to Smart Control Center, but nothing shows up. I've tried the default IP's I can find in the documentation (192.168.0.239 and 192.168.1.1) and I can't access the web interface. Obviously, something went wrong in the upgrade process, but I'm really not sure how to even troubleshoot since the switch is basically non-responsive to anything I do.GS724TPv3 The switch loses IP connection about 1 time in 5 days.
Hi, I have Netgear switch GS724TPv3, newest firmware installed The switch loses IP connection about 1 x every 5 days. I don't know why? While power supply of IP cameras powered via POE is maintained. IP connectivity from router and connected devices to switch is lost. After hard power off and on of switch everything works. The restart pin on the front of switch does not restore connectivity, it requires complete power off. The switch has a static IP address to avoid problems with address reservation from DHCP router. Looking for a solution to the problem of setting up a reboot script for switch GS724TPv3 from my NAS Synology via ssh or telnet. Can someone with experience help me with writing a script. Thank you Zbynek