[OneDumDuk]

Router/Version: Linksys EA8300
File/Kernel: Linux 4.9.337 #3569 SMP Sat Jan 3 12:03:49 +07 2026 armv7l
Previous/Reset: r63230 Reset & manual reconfigure, hasn't been done since r58531.
Mode/Status: Wired access point. No WAN, No DHCP, No DNSMasq, No USB, No VPN, No firewall, No WDS, No logging.
Issues/Errors: After several hours - None that I have noticed.

[Be Inspired]

Hello to all,

Upgraded both of my devices to this build from r63230 without reset and all i use are working fine.

Thank you very much BS and devs.

[dplotz]

Router/Version: Linksys MR7350 x 3
File/Kernel: DD-WRT v3.0-r63257 std (01/03/26), Linux 6.6.119-rt29 #4940 SMP Sat Jan 3 14:56:25 +07 2026 aarch64
Previous/Reset: DD-WRT v3.0-r61848 std (06/24/25), full reset on gateway
Mode/Status: Gateway (NSS-ECM), Access Point (2.4GHz-HT20 N/G Mixed, 5GHZ-VHT80 AX/AC/N mixed, WPA2/WPA3, 802.11r/v/k, guest network, domain:UNITED STATES), performance governor, IPV6 (DHCP6 w/ prefix delegation), Entware, DOT via SmartDNS/DNSMasq, OpenVPN server, Wireguard Server + 2 Wired access points (2.4GHz-HT20 AX Only, 5GHZ-HT80 AX/AC/N mixed, WPA2/WPA3, 802.11r/v/k, guest network, domain:UNITED STATES)
Issues/Errors:
Up 3 hours. USB 3.2 stick working properly for Entware and "jffs" partitions. Speed, wired and wifi, is very close to published, which is equal or favorable to the ISP router - tested via nPerf.com. Wireguard and OpenVPN servers both working as expected and throughput sufficient to open video files on network shares. 5GHz showing 22dBm (set to 27dBm). 2.4GHz showing 25dBm (also set to 27dBm).

Not getting an IPv6 address on this build, even after full reset with basic config. I was getting one in r63230, even if that firmware was a little flaky with DNS. Left it for a while to see if it would eventually pick one up, but it didn't. Rolled back to r61848. On the gateways, I had one gateway go completely unresponsive after I hit Apply on the Networking tab. Had to do a hard reset. Rolled those back as well.

Thank you Brainslayer.

[pbphoto]

Router/Version: Netgear R7800 (x2) DD-WRT v3.0-r63257 std (01/03/26)
Kernel: Linux Linux 6.1.159-rt28 #745 SMP Sat Jan 3 12:27:11 +07 2026 armv7l
Previous/Reset: DD-WRT v3.0-r63020 std (12/10/25) no reset
Mode/Status: 'router' operating mode / wifi AP 802.11rvk + usteer / default networking / SFE disabled / Firewall disabled
Uptime: 11 hours but issue below happens within an hour
Issues/Errors: Both my R7800s are experiencing VANILLA wifi driver restarts on both radios on this release and the previous 63230 too. sometimes the radio comes back online, sometimes it says it successfully recovered but no clients can connect. The first message in the syslog during the event is the "excessive missing ACKs". Sample dmesg and syslog output below.

UPDATE: 1/16/2026 - with the r63355 release, these driver resets continued. I tried the DD-WRT firmware, and that fixed this problem.

SYSLOG:
Jan 3 21:15:23.209 boydrouter2 daemon.info hostapd: wlan0: STA be:cf:eb:7c:7b:8a IEEE 802.11: disconnected due to excessive missing ACKs
Jan 3 21:15:23.255 boydrouter2 daemon.info hostapd: wlan0: STA be:cf:eb:7c:7b:8a IEEE 802.11: disconnected due to excessive missing ACKs
Jan 3 21:15:53.256 boydrouter2 daemon.info hostapd: wlan0: STA be:cf:eb:7c:7b:8a IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Jan 3 21:15:58.411 boydrouter2 daemon.info hostapd: wlan0: STA 7e:63:28:82:14:ff IEEE 802.11: disconnected due to excessive missing ACKs
Jan 3 21:15:58.445 boydrouter2 daemon.info hostapd: wlan0: STA 7e:63:28:82:14:ff IEEE 802.11: disconnected due to excessive missing ACKs
Jan 3 21:16:28.446 boydrouter2 daemon.info hostapd: wlan0: STA 7e:63:28:82:14:ff IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Jan 3 21:18:43.822 boydrouter2 daemon.info hostapd: wlan0: STA be:cf:eb:7c:7b:8a IEEE 802.11: authenticated
Jan 3 21:18:43.826 boydrouter2 daemon.info hostapd: wlan0: STA be:cf:eb:7c:7b:8a IEEE 802.11: associated (aid 2)
Jan 3 21:18:43.836 boydrouter2 daemon.info hostapd: wlan0: STA be:cf:eb:7c:7b:8a RADIUS: starting accounting session 8B93D7B4EF46B301
Jan 3 21:18:43.836 boydrouter2 daemon.info hostapd: wlan0: STA be:cf:eb:7c:7b:8a WPA: pairwise key handshake completed (RSN)
Jan 3 21:21:08.111 boydrouter2 daemon.info hostapd: wlan1: STA 64:1c:b0:b1:6d:4d IEEE 802.11: authenticated
Jan 3 21:21:08.114 boydrouter2 daemon.info hostapd: wlan1: STA 64:1c:b0:b1:6d:4d IEEE 802.11: associated (aid 1)
Jan 3 21:21:08.208 boydrouter2 daemon.info hostapd: wlan1: STA 64:1c:b0:b1:6d:4d RADIUS: starting accounting session EDF37D7CA0044302
Jan 3 21:21:08.208 boydrouter2 daemon.info hostapd: wlan1: STA 64:1c:b0:b1:6d:4d WPA: pairwise key handshake completed (RSN)
Jan 3 21:26:21.795 boydrouter2 daemon.info hostapd: wlan0: STA ca:cf:38:49:8a:40 IEEE 802.11: authenticated
Jan 3 21:26:22.291 boydrouter2 daemon.info hostapd: wlan0: STA ca:cf:38:49:8a:40 IEEE 802.11: associated (aid 3)
Jan 3 21:26:22.305 boydrouter2 daemon.info hostapd: wlan0: STA ca:cf:38:49:8a:40 RADIUS: starting accounting session EF430F554F363BE8
Jan 3 21:26:22.306 boydrouter2 daemon.info hostapd: wlan0: STA ca:cf:38:49:8a:40 WPA: pairwise key handshake completed (RSN)
Jan 3 21:34:07.437 boydrouter2 daemon.notice hostapd: wlan1: STA be:cf:eb:7c:7b:8a IEEE 802.11: did not acknowledge authentication response
Jan 3 21:34:07.476 boydrouter2 daemon.notice hostapd: wlan1: STA be:cf:eb:7c:7b:8a IEEE 802.11: did not acknowledge authentication response
Jan 3 21:34:07.557 boydrouter2 daemon.notice hostapd: wlan1: STA be:cf:eb:7c:7b:8a IEEE 802.11: did not acknowledge authentication response
Jan 3 21:34:07.558 boydrouter2 daemon.notice hostapd: wlan1: STA be:cf:eb:7c:7b:8a IEEE 802.11: did not acknowledge authentication response
Jan 3 21:34:07.558 boydrouter2 daemon.notice hostapd: wlan1: STA be:cf:eb:7c:7b:8a IEEE 802.11: did not acknowledge authentication response
Jan 3 21:34:08.105 boydrouter2 daemon.info hostapd: wlan1: STA ca:cf:38:49:8a:40 IEEE 802.11: associated (aid 2)
Jan 3 21:34:08.164 boydrouter2 daemon.info hostapd: wlan1: STA ca:cf:38:49:8a:40 RADIUS: starting accounting session 024A623C0CF387E0
Jan 3 21:34:08.164 boydrouter2 daemon.info hostapd: wlan1: STA ca:cf:38:49:8a:40 WPA: pairwise key handshake completed (RSN)
Jan 3 21:34:09.847 boydrouter2 daemon.info hostapd: wlan0: STA be:cf:eb:7c:7b:8a IEEE 802.11: disconnected due to excessive missing ACKs
Jan 3 21:34:09.927 boydrouter2 daemon.info hostapd: wlan0: STA be:cf:eb:7c:7b:8a IEEE 802.11: disconnected due to excessive missing ACKs
Jan 3 21:34:10.649 boydrouter2 daemon.info hostapd: wlan0: STA 5c:c1:d7:ca:1b:98 IEEE 802.11: authenticated
Jan 3 21:34:10.748 boydrouter2 daemon.info hostapd: wlan0: STA 5c:c1:d7:ca:1b:98 IEEE 802.11: associated (aid 1)
Jan 3 21:34:10.759 boydrouter2 daemon.info hostapd: wlan0: STA 5c:c1:d7:ca:1b:98 RADIUS: starting accounting session A2F85435A23E7912
Jan 3 21:34:10.759 boydrouter2 daemon.info hostapd: wlan0: STA 5c:c1:d7:ca:1b:98 WPA: pairwise key handshake completed (RSN)
Jan 3 21:34:14.999 boydrouter2 daemon.info hostapd: wlan0: STA ca:cf:38:49:8a:40 IEEE 802.11: authenticated
Jan 3 21:34:15.003 boydrouter2 daemon.info hostapd: wlan0: STA ca:cf:38:49:8a:40 IEEE 802.11: associated (aid 3)
Jan 3 21:34:15.051 boydrouter2 daemon.info hostapd: wlan0: STA ca:cf:38:49:8a:40 RADIUS: starting accounting session EF430F554F363BE8
Jan 3 21:34:15.051 boydrouter2 daemon.info hostapd: wlan0: STA ca:cf:38:49:8a:40 WPA: pairwise key handshake completed (RSN)
Jan 3 21:34:18.040 boydrouter2 daemon.info hostapd: wlan0: STA be:cf:eb:7c:7b:8a IEEE 802.11: authenticated
Jan 3 21:34:18.045 boydrouter2 daemon.info hostapd: wlan0: STA be:cf:eb:7c:7b:8a IEEE 802.11: associated (aid 2)
Jan 3 21:34:18.055 boydrouter2 daemon.info hostapd: wlan0: STA be:cf:eb:7c:7b:8a RADIUS: starting accounting session 8B93D7B4EF46B301
Jan 3 21:34:18.055 boydrouter2 daemon.info hostapd: wlan0: STA be:cf:eb:7c:7b:8a WPA: pairwise key handshake completed (RSN)
Jan 3 21:34:45.035 boydrouter2 daemon.info hostapd: wlan1: STA ca:cf:38:49:8a:40 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Jan 3 21:34:48.046 boydrouter2 daemon.info hostapd: wlan1: STA be:cf:eb:7c:7b:8a IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)


DMESG:
[ 2677.332613] ath10k_pci 0000:01:00.0: qca9984/qca9994 hw1.0 target 0x01000000 chip_id 0x00000000 sub 168c:cafe
[ 2677.332627] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
[ 2677.335052] ath10k_pci 0000:01:00.0: firmware ver 10.4-3.20-00008 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate crc32 aa899c87
[ 2677.335897] ath10k_pci 0000:01:00.0: board_file api 2 bmi_id 0:1 crc32 2578b9d0
[ 2677.335904] ath10k_pci 0000:01:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 512 raw 0 hwcrypto 1
[ 2677.491867] ieee80211 phy0: Hardware restart was requested
[ 2679.884389] ath10k_pci 0000:01:00.0: boot get otp board id result 0x00040400 board_id 1 chip_id 0 ext_bid_support 1
[ 2682.149842] ath10k_pci 0000:01:00.0: boot upload otp to 0x1234 len 9317
[ 2685.693789] ath10k_pci 0000:01:00.0: Init Max Stations to 512
[ 2685.693802] ath10k_pci 0000:01:00.0: wmi event service ready min_tx_power 0x0000003f max_tx_power 0x0000003f ht_cap 0x0000185b vht_cap 0x339b79fa vht_supp_mcs 0x0000ffaa sw_ver0 0x01000000 sw_ver1 0x00000008 fw_build 0x00000000 phy_capab 0x00000001 num_rf_chains 0x00000004 eeprom_rd 0x00000000 low_2ghz_chan 2312 high_2ghz_chan 2732 low_5ghz_chan 4912 high_5ghz_chan 6100 num_mem_reqs 0x00000009 min_pkt_size_enable 0x00000000
[ 2685.770025] ath10k_pci 0000:01:00.0: wmi event ready sw_version 0x01000000 abi_version 3 mac_addr a0:04:60:21:4c:59 status 0
[ 2685.874324] ath10k_pci 0000:01:00.0: Init Channel Number 31
[ 2685.910769] ath10k_pci 0000:01:00.0: set base mac addr a0:04:60:21:4c:59
[ 2685.911514] ath10k_pci 0000:01:00.0: bdf failsafe status event received from fw: 0
[ 2685.943279] ath10k_pci 0000:01:00.0: mac txpower 23
[ 2686.222374] ath10k_pci 0000:01:00.0: mac txpower 23
[ 2686.243592] ath10k_pci 0000:01:00.0: device successfully recovered
[ 2686.243602] ath10k_pci 0000:01:00.0: mac txpower 23
[ 3009.561556] ieee80211 phy1: Hardware restart was requested
[ 3012.004261] ath10k_pci 0001:01:00.0: boot get otp board id result 0x00040800 board_id 2 chip_id 0 ext_bid_support 1
[ 3014.338832] ath10k_pci 0001:01:00.0: boot upload otp to 0x1234 len 9317
[ 3017.960163] ath10k_pci 0001:01:00.0: Init Max Stations to 512
[ 3017.960176] ath10k_pci 0001:01:00.0: wmi event service ready min_tx_power 0x0000003f max_tx_power 0x0000003f ht_cap 0x0000185b vht_cap 0x339b79b2 vht_supp_mcs 0x0000ffaa sw_ver0 0x01000000 sw_ver1 0x00000008 fw_build 0x00000000 phy_capab 0x00000002 num_rf_chains 0x00000004 eeprom_rd 0x00000000 low_2ghz_chan 2312 high_2ghz_chan 2732 low_5ghz_chan 4912 high_5ghz_chan 6100 num_mem_reqs 0x00000009 min_pkt_size_enable 0x00000000
[ 3018.038316] ath10k_pci 0001:01:00.0: wmi event ready sw_version 0x01000000 abi_version 3 mac_addr a0:04:60:21:4c:5a status 0
[ 3018.177800] ath10k_pci 0001:01:00.0: Init Channel Number 11
[ 3018.177878] ath10k_pci 0001:01:00.0: set base mac addr a0:04:60:21:4c:5a
[ 3018.178225] ath10k_pci 0001:01:00.0: bdf failsafe status event received from fw: 0
[ 3018.216473] ath10k_pci 0001:01:00.0: mac txpower 23
[ 3018.218553] ath10k_pci 0001:01:00.0: mac txpower 23
[ 3018.491646] ath10k_pci 0001:01:00.0: mac txpower 23
[ 3018.493987] ath10k_pci 0001:01:00.0: qca9984/qca9994 hw1.0 target 0x01000000 chip_id 0x00000000 sub 168c:cafe
[ 3018.493997] ath10k_pci 0001:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
[ 3018.496466] ath10k_pci 0001:01:00.0: firmware ver 10.4-3.20-00008 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate crc32 aa899c87
[ 3018.497390] ath10k_pci 0001:01:00.0: board_file api 2 bmi_id 0:2 crc32 2578b9d0
[ 3018.497399] ath10k_pci 0001:01:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 512 raw 0 hwcrypto 1
[ 3018.541675] ath10k_pci 0001:01:00.0: mac txpower 23
[ 3018.541792] wlan1: failed to set key (1, ff:ff:ff:ff:ff:ff) to hardware (-108)
[ 3018.541804] wlan1: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-108)
[ 3018.541837] wlan1.1: failed to set key (1, ff:ff:ff:ff:ff:ff) to hardware (-108)
[ 3018.541847] wlan1.1: failed to set key (2, ff:ff:ff:ff:ff:ff) to hardware (-108)
[ 3018.541935] ath10k_pci 0001:01:00.0: mac txpower 23

[James Greystone]

[AsX]

Ditto here on my 7800.

[KACTET]

Router/Version: TP-Link TL-WR841ND v11
Update method: WebUpgrade
File/Kernel: tl-wr841nd-webflash.bin_r63257 / Linux 3.18.140-d6 #256289 Sat Jan 3 16:17:33 +07 2026 mips
Previous/Reset: r63230 / no
Mode/Status: AP wired and wireless / Up and running for 5:28
Issues/Errors: Nothing significant

If your router's light turns red, don't worry. Internet connection is ok.
Incorrect rate of wlan0 - 800 Mbit/s!

Thank you BS and gurus!

[Alozaros]

My XR500 both radios still standing and no client drops no error, country domain HAITI..
can share settings if so...

[Megazildjian]

Router/Version: Linksys MX4300
Firmware: r63257
Previous/Reset: r62606 / No
Mode: Gateway
Issues/Errors: IPv6 is broken due to dhcp6c startup failure. It appears enabled in the GUI and an IPv6 address is shown at the top right, but there is no IPv6 internet connectivity on LAN. WireGuard (IPv4-only) also loses connectivity when IPv6 is enabled.

Syslog shows:
Linksys user.err: error starting threads: errno 2 (No such file or directory)

After running some terminal cmds, it looks like the dhcp6c IPv6 client or a required runtime dependency/config is missing or failing to initialize. Kernel IPv6 remains enabled, but the userspace DHCPv6 client does not function, resulting in silent IPv6 failure.

Reverting to r62606 restores full IPv6 and WireGuard functionality, since IPv6 WAN is handled correctly by the dhcp6c client.

EDIT: Adding the following to save firewall fixed IPv6 but still no idea why wireguard has no internet.

[kernel-panic69]

[Per Yngve Berg]

The 5Ghz on my R7800 didn't come up. switching to "Vanilla" fixed it.

[IONK]

[kernel-panic69]

[IONK]

[kulica64]

Netgear R9000 usb printer sharing does not work on 6.12.x kernel. Rewerted back to Linux 4.9.337 and everything works normally. Plus on the 6.12 also the lsusb command does not work. I also saw LEDs turning off and then back on although uptime was not affected by it.