Posted: Fri Oct 24, 2025 15:54 Post subject: New Build - 10/24/2025 - r62418
Welcome to Atheros r62418 beta release thread for reporting, feedback to developers and community benefit.
Please do not flash builds until installation is understood, risks involved and device specificrecovery methods.
Avoid discussions, create threads for questions, general problems or use search; this thread is not for support.
List router model & version or revision, operating & wireless modes & exact filename/firmware image flashed.
CLI Flash: 'cd /tmp' then 'wget {file URL}' (httponly) or 'curl -O {file URL}' (http, https, ftp) 'write {file} linux' then 'reboot'.
Issues, observations, and/or workarounds reported:
• WebUI: Clear history or use a portable. Temporary cache bypass: Ctrl+F5, Cmd+Shift+R or new private window/incognito.
• Please report findings with steps needed to reproduce, configuration, clients, output, logs and important information below!
Important:
• Detail issues & relevant configs, logs: syslog klog 'dmesg' 'cat /tmp/var/log/messages' nvram set console_debug=1, serial.
• Firewall NAT: 'iptables -vnL' 'iptables -t nat -vnL' 'iptables -t mangle -vnL' & 'cat /tmp/.ipt'. Debug Analyze: stracetcpdump.
• Gremlins: reboot. cold boot. Reset & reconfigure not restore backup. Search Trac & discuss in forum before opening tickets.
• Include operating & wireless modes (e.g. Gateway, Router, AP, SB, WDS, Mesh) and applicable configurations to reproduce.
Router/Version: Linksys MR7350
File: dd-wrt-webupgrade.bin
Firmware: DD-WRT v3.0-r62418 std (10/24/25) (prev. DD-WRT v3.0-r62374 std (10/19/25))
Kernel: Linux 6.6.113-rt29 #4378 SMP Fri Oct 24 04:21:03 +07 2025 aarch64
Mode: Gateway, SFE disabled, 2.4G (20MHz mixed, WPA2 Personal, WPA3 Personal / SAE - CCMP-128 (AES)) and 5G (80MHz AX / AC / N Mixed, WPA3 Personal / SAE - CCMP-128 (AES)) wifi, bridged VAP on 2.4GHz, Wireguard for external access, WAN disabled, DISABLED Keep Alive reboot 6:02 in the morning, using my own local NTP
Reset: No
Status: Installed today.
I had to restart this router several times after installation, both WLANs were slow and sluggish.
Some wireless devices had problems to connect to www, "Status" --> "Wireless" did show the "0 SNR / Signal Quality / RX Rate" Problem.
Others did not connect at all.
No new entries in its oops partition
But Syslog (read messages and messages.0) filled fast with HUNDREDS of entries like this:
Code:
Oct 25 10:49:52.232 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan0
Oct 25 10:49:57.235 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan0
Oct 25 10:50:02.239 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan0
Oct 25 10:50:07.242 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan0
Oct 25 10:50:12.248 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan0
Oct 25 10:50:17.252 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan0
Oct 25 10:50:22.255 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan0
Oct 25 10:50:27.259 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan0
Oct 25 10:50:32.263 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan0
Oct 25 10:50:37.266 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan0
Oct 25 10:50:42.270 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan0
Oct 25 10:50:47.273 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan0
After several reboot filled with this
Code:
Oct 25 13:06:06.716 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan1.1
Oct 25 13:06:06.717 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan1.1
Oct 25 13:06:06.717 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan1
Oct 25 13:06:11.723 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan1.1
Oct 25 13:06:11.723 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan1.1
Oct 25 13:06:11.723 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan1
Oct 25 13:06:16.727 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan1.1
Oct 25 13:06:16.727 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan1.1
Oct 25 13:06:16.727 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan1
Oct 25 13:06:21.730 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan1.1
Oct 25 13:06:21.730 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan1.1
Oct 25 13:06:21.730 MR7350 user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan1
Rebooted the router a few times and now all devices seem to work.
The overall signal quality for WLAN0 / 5GHz is low, even in same room no device has above 60%.
I increased tx power to 23dBm, but no bigger changes to quality. Maybe like 5%?.
For doubling the output power in like ~3 meter distance this is strange.
Joined: 04 Dec 2007 Posts: 1272 Location: Murrysville, PA
Posted: Sat Oct 25, 2025 14:34 Post subject:
Zyxx wrote:
The overall signal quality for WLAN0 / 5GHz is low, even in same room no device has above 60%.
I increased tx power to 23dBm, but no bigger changes to quality. Maybe like 5%?.
For doubling the output power in like ~3 meter distance this is strange.
Keep in mind that signal strength (ie., output power) does not equate to signal quality. In some cases they can be opposite. Judge your WiFi by things like a speed test. Try setting your power outputs to 20db and see if devices can connect. Then do a speedtest if you can. Raise the power by 2 or three and do it again. Find a sweet spot.
Yes, I know what I am talking about and have done this. I got better performance by actually lowering my power output. (For those lurking, increased power output can also increase noise and interference. That will degrade your overall performance even though you have a a huge power output.) _________________ Linksys MX8500 DD-WRT v3.0-r64453 std (04/14/26)
Linux 6.12.81 #131 SMP Tue Apr 14 13:42:15 +06 2026 aarch64 Gateway, AP, DNSMasq, no SmartDNS, NSS-ECM, QCA NSS, no STP
VAP on wlan1 for internet devices
Static Leases & DHCP
Cloudflare DoH, No QoS, No Forced DoT, 802.11k
2.4GHz: AP, AX Only, ACK Timing 300, WPA2 & WPA3 w/AES & GCMP
5GHz: AP, AX Only, ACK Timing 300, WPA2 & WPA3 w/AES & GCMP
Netgear AX1800 WiFi Mesh Extender (x2)
Xfinity 1.2Gbps/40Mbps
@MLandi, thank you for your thoughts on this.
I know, increasing (doubling) the output power is not the right solution.
Just did it for tests and after this went back to default, 20 dBm here in my country.
I wanted to state: Something feels off. A few releases back WLAN0 signal quality was better in my opinion.
But given all the changes and active work being done on ath11k... who knows.
Joined: 04 Dec 2007 Posts: 1272 Location: Murrysville, PA
Posted: Sun Oct 26, 2025 1:38 Post subject:
Zyxx wrote:
I wanted to state: Something feels off. A few releases back WLAN0 signal quality was better in my opinion.
But given all the changes and active work being done on ath11k... who knows.
What is your gauge of signal quality? Consider that it may be off or otherwise different than before. _________________ Linksys MX8500 DD-WRT v3.0-r64453 std (04/14/26)
Linux 6.12.81 #131 SMP Tue Apr 14 13:42:15 +06 2026 aarch64 Gateway, AP, DNSMasq, no SmartDNS, NSS-ECM, QCA NSS, no STP
VAP on wlan1 for internet devices
Static Leases & DHCP
Cloudflare DoH, No QoS, No Forced DoT, 802.11k
2.4GHz: AP, AX Only, ACK Timing 300, WPA2 & WPA3 w/AES & GCMP
5GHz: AP, AX Only, ACK Timing 300, WPA2 & WPA3 w/AES & GCMP
Netgear AX1800 WiFi Mesh Extender (x2)
Xfinity 1.2Gbps/40Mbps
Trying to troubleshoot the instability that I've seen in recent builds, I started with a full wipe of my gateway router and minimum necessary config (IPv4 only, SFE, no VAPs, br0 only, DDNS, port forwarding). After 12 hours, I added IPv6. Wifi is working as expected and very stable, although there are only 2 devices connected to the gateway router, most devices connect to my WAPs (which are still running 61818). Tomorrow morning, I'll add back OpenVPN and Wireguard servers. I expect that the issues I was previously seeing are related to either SmartDNS or br1 guest network. Those will be added back individually after I've confirmed that everything else is stable. Last, I'll enable NSS-ECM. I'll try to determine where it flakes out. Logging to Visual Syslog Server, so when/if it blows up, I should have a record.
Thank you Brainslayer. _________________ Formerly dpp3530 Linksys MX4300
Gateway, 2 wired APs, NSS-ECM , Clock 1382MHz
VAPs on wlan0 and wlan1 for guest/IOT devices
IPv4 & IPv6 (Prefix Delegation)
Static Leases & DHCP
SmartDNS (DOT using NextDNS, Cloudflare), DNSMasq
Wireguard and OpenVPN server
2.4GHz: dd-wrt, AX Only, ACK Timing 1350, WPA3 SAE & WPA2 w/AES
5GHz: dd-wrt, AX/AC/N Mixed, ACK Timing 1350, WPA3 SAE & WPA2 w/AES
Verizon Fios, 500/500Mbps
What is your gauge of signal quality? Consider that it may be off or otherwise different than before.
Example:
I sit with this tablet like 4m away and can see router.
Status --> Wireless reads like 36% signal quality for 5GHz WLAN and if I connect to 2.4GHz 72%.
This does depend on the device used and me, where I hold the tablet ofc. Its internal antenna arent the best too.
I know a few months ago I had like 5x% signal quality with wireless 5GHz and this very same device, while 2.4GHz sitting in the 7x% region.
Maybe humidity is a thing... currently sitting at like 65%, it is raining since days.
Joined: 07 Jan 2025 Posts: 260 Location: Bethel Park, PA, USA
Posted: Sun Oct 26, 2025 21:40 Post subject:
I'm seeing this in my logs, and my IOT devices can't connect to 2.4GHz on the gateway.
Code:
192.168.6.1 Oct 26 16:03:11 daemon info dnsmasq-dhcp[2808] DHCPACK(br0) 192.168.6.96 2c:05:47:2f:53:95
192.168.6.1 Oct 26 20:03:11 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:03:15 daemon info hostapd wlan1: STA 2c:05:47:2f:53:95 IEEE 802.11: disassociated
192.168.6.1 Oct 26 20:03:50 daemon info hostapd wlan1: STA 2c:05:47:2f:53:95 IEEE 802.11: authenticated
192.168.6.1 Oct 26 20:03:50 daemon info hostapd wlan1: STA 2c:05:47:2f:53:95 IEEE 802.11: associated (aid 1)
192.168.6.1 Oct 26 20:03:51 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:03:52 daemon info hostapd wlan1: STA 2c:05:47:2f:53:95 RADIUS: starting accounting session AAD5EA6EDC871A87
192.168.6.1 Oct 26 20:03:52 daemon info hostapd wlan1: STA 2c:05:47:2f:53:95 WPA: pairwise key handshake completed (RSN)
192.168.6.1 Oct 26 16:03:52 daemon info dnsmasq-dhcp[2808] DHCPDISCOVER(br0) 2c:05:47:2f:53:95
192.168.6.1 Oct 26 16:03:52 daemon info dnsmasq-dhcp[2808] DHCPOFFER(br0) 192.168.6.96 2c:05:47:2f:53:95
192.168.6.1 Oct 26 16:03:52 daemon info dnsmasq-dhcp[2808] DHCPREQUEST(br0) 192.168.6.96 2c:05:47:2f:53:95
192.168.6.1 Oct 26 16:03:52 daemon info dnsmasq-dhcp[2808] DHCPACK(br0) 192.168.6.96 2c:05:47:2f:53:95
192.168.6.1 Oct 26 20:03:56 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:04:01 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:04:06 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:04:11 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:04:16 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:04:21 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:04:26 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:04:31 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:04:36 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:04:41 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:04:46 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:04:51 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:04:56 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:05:01 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:05:06 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:05:11 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:05:16 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:05:21 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:05:26 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:05:31 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:05:36 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:05:41 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:05:46 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:05:51 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:05:56 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:06:01 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:06:06 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:06:11 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:06:16 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:06:22 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:06:27 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:06:32 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:06:37 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:06:42 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:06:42 daemon info hostapd wlan1: STA 2c:05:47:2f:53:95 IEEE 802.11: authenticated
192.168.6.1 Oct 26 20:06:42 daemon info hostapd wlan1: STA 2c:05:47:2f:53:95 IEEE 802.11: associated (aid 1)
192.168.6.1 Oct 26 20:06:45 daemon info hostapd wlan1: STA 2c:05:47:2f:53:95 IEEE 802.11: disassociated
192.168.6.1 Oct 26 20:07:03 daemon info hostapd wlan1: STA 2c:05:47:2f:53:95 IEEE 802.11: authenticated
192.168.6.1 Oct 26 20:07:03 daemon info hostapd wlan1: STA 2c:05:47:2f:53:95 IEEE 802.11: associated (aid 1)
192.168.6.1 Oct 26 20:07:04 daemon info hostapd wlan1: STA 2c:05:47:2f:53:95 RADIUS: starting accounting session 3AE29EAE8EED1803
192.168.6.1 Oct 26 20:07:04 daemon info hostapd wlan1: STA 2c:05:47:2f:53:95 WPA: pairwise key handshake completed (RSN)
192.168.6.1 Oct 26 16:07:04 daemon info dnsmasq-dhcp[2808] DHCPDISCOVER(br0) 2c:05:47:2f:53:95
192.168.6.1 Oct 26 16:07:04 daemon info dnsmasq-dhcp[2808] DHCPOFFER(br0) 192.168.6.96 2c:05:47:2f:53:95
192.168.6.1 Oct 26 16:07:04 daemon info dnsmasq-dhcp[2808] DHCPREQUEST(br0) 192.168.6.96 2c:05:47:2f:53:95
192.168.6.1 Oct 26 16:07:04 daemon info dnsmasq-dhcp[2808] DHCPACK(br0) 192.168.6.96 2c:05:47:2f:53:95
192.168.6.1 Oct 26 20:07:07 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:07:12 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:07:17 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:07:22 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:07:27 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:07:32 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:07:37 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:07:42 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:07:47 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:07:52 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:07:57 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:08:02 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:08:07 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:08:12 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:08:17 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:08:22 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:08:27 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:08:32 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:08:37 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:08:42 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:08:47 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:08:52 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:08:57 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:09:02 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:09:07 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:09:12 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:09:17 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:09:22 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:09:27 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:09:32 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:09:37 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:09:42 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:09:47 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:09:52 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:09:57 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:10:02 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:10:07 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:10:12 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:10:17 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:10:22 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:10:27 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:10:32 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:10:37 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:10:42 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:10:47 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:10:52 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:10:57 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:11:02 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:11:07 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:11:12 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:11:17 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:11:22 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:11:27 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:11:32 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:11:37 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
192.168.6.1 Oct 26 20:11:42 user err [ath11k_watchdog] : zero signal issue detected on interface wlan1
Joined: 07 Jan 2025 Posts: 260 Location: Bethel Park, PA, USA
Posted: Mon Oct 27, 2025 17:35 Post subject:
dplotz wrote:
I'm seeing this in my logs, and my IOT devices can't connect to 2.4GHz on the gateway.
A reboot didn't fix the "zero signal" issue nor did a full power cycle. I temporarily swapped back to my working device running r61848. I decided to give it a try again this afternoon, so I swapped back to the test device. When I powered it on, the "zero signal" was back.
The last thing I had turned on before the issue started was USB storage support (thumbdrive with entware on it). I turned that back off and pulled the USB drive out, then did a reboot from the GUI. My smart doorbell connected in less than a minute and the errors completely stopped.
It's possible this is just a weird coincidence, but it worked for almost 2 days before I turned on USB, and works again as soon as I turn USB off. I know correlation does not equal causation, but it's certainly an intriguing finding. _________________ Formerly dpp3530 Linksys MX4300
Gateway, 2 wired APs, NSS-ECM , Clock 1382MHz
VAPs on wlan0 and wlan1 for guest/IOT devices
IPv4 & IPv6 (Prefix Delegation)
Static Leases & DHCP
SmartDNS (DOT using NextDNS, Cloudflare), DNSMasq
Wireguard and OpenVPN server
2.4GHz: dd-wrt, AX Only, ACK Timing 1350, WPA3 SAE & WPA2 w/AES
5GHz: dd-wrt, AX/AC/N Mixed, ACK Timing 1350, WPA3 SAE & WPA2 w/AES
Verizon Fios, 500/500Mbps
Joined: 07 Jan 2025 Posts: 260 Location: Bethel Park, PA, USA
Posted: Mon Oct 27, 2025 18:47 Post subject:
As soon as I added a VAP and br1, the "zero signal" issue came back. Could this be a resource constraint of some sort? _________________ Formerly dpp3530 Linksys MX4300
Gateway, 2 wired APs, NSS-ECM , Clock 1382MHz
VAPs on wlan0 and wlan1 for guest/IOT devices
IPv4 & IPv6 (Prefix Delegation)
Static Leases & DHCP
SmartDNS (DOT using NextDNS, Cloudflare), DNSMasq
Wireguard and OpenVPN server
2.4GHz: dd-wrt, AX Only, ACK Timing 1350, WPA3 SAE & WPA2 w/AES
5GHz: dd-wrt, AX/AC/N Mixed, ACK Timing 1350, WPA3 SAE & WPA2 w/AES
Verizon Fios, 500/500Mbps
This zero issue raised its head after r61848.
I tried nvram erase, made simple configs, left out my VAPs, to no avail.
If this zero issue appears I have to restart my MR7350 one to four or even five times until everything is working again.
Then it will work until next reboot is done... starting the gamble anew.
This happens with other domains, channels, Ciphers, security settings and I'm at a loss.
I remade the config so often by hand over the last weeks... sometimes it just happens.
Currently we can only wait for a bugfix in my opinion.
It feels good seing this issue being acknowledged by being added as warning in syslog.
