Posted: Thu Oct 23, 2025 13:35 Post subject: WR841ND
Router/Version: TP-Link TL-WR841ND v11
Update method: WebUpgrade
File/Kernel: tl-wr841nd-webflash.bin_r62374 / Linux 3.18.140-d6 #248645 Sun Oct 19 07:41:31 +07 2025 mips
Previous/Reset: r62365 / no
Mode/Status: AP wired and wireless / Up and running for 7:20
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! _________________ Atheros
Netgear XR500 Nighthawk - DD-WRT 63257
Tp-Link TL-WDR4900 v1.3 - DD-WRT 53133
TP-Link WR1043ND v4 - DD-WRT 51838
TP-Link WR1043ND v2 - Gargoyle OS 1.13.0
TP-Link WR841ND v11 - DD-WRT 63257
Broadcom
Asus RT-AC88U - DD-WRT 63257
Asus RT-AC87U R - DD-WRT 63257
Asus RT-N66U - DD-WRT 63257
Linksys WRT54GL v1.1 - DD-WRT 54517M
Linksys WRT54GL v1.1 - FreshTomato 2023.4_MIPS_K26
Linksys WRT54GL v1.1 - Gargoyle OS 1.6.2
Issues/Errors: Seems that the WAN port on my OG R9000 has gone bye bye. So swapped in the spare. Was running stock Netgear firmware, flashed it direct to latest and uploaded the config backup from the "faulty" unit
UPDATE: I was fiddling around with wireguard tunnels - I run two by default but was playing with a config for a third with multiple clients when the "new" R9000 did the exact same unable to connect to my cable modem malarkey as the "old" R9000 - stops passing traffic, can't renew a lease, won't get a lease if I reboot the router.
The old R9000 had started working again after a factory reset so that's what I did with the new one - immediately upon reboot, connected, received DHCP lease and started working. I uploaded the config taken from the old router a couple of days ago, rebooted again and it's working as expected.
IPv6 DHCPv6 still kills IPv4 transit for some reason still. Might have to try that one with a defaulted configuration another day.
I came here to report something else...but...
I "THINK" there is an issue with adding, changing wireguard tunnels on the gui wireguard pages as I a few months ago had unexpected changes happening while playing around in there, saving, changing and then upon reboot had an issue with some settings not being correct. I just 2 days ago ran into the same thing where I think its changing something that isnt supposed to be and causing problems. I have to search and muck about with it, but between myself and other reports now...something is wrong. Im gonna play with it tonight as I documented it for myself but dont have the notes till tonight to look at. My memory is garbage now so I write stuff down, but I remember that I broke things, just cant remember how.
But in essence I tried to just add a new device and it broke my two pre existing tunnels. They connect but dont work remotely meaning they dont give remote lan access. Since I was unfortunately dealing with lawyers for 2 days I didnt have time to play with it, but I think it unchecks a box and its that simple but a box you dont expect to be unchecked or such...Anyway fyi for those that are keeping an eye on it.
Router Model 3x MX4300 and gateway, wap/vap and switch, 3x as mesh wap providers
Firmware Version DD-WRT v3.0-r62240 std (10/04/25) AND v3.0-r62374 std (10/19/25)
update: GUI
reset: NO
mode: Gateway, WAP,VAP, dhcp server, wireguard server and nordvpn (via OpenVPN) client
So strange issue...upgraded all but primary router to 62374 but I think the problem is with that version.
Fire tablet that has mostly worked fine connecting is now getting a
Code:
Oct 23 15:05:27.983 DD-WRTsean daemon.notice hostapd: wlan2: STA e0:f7:xxxxx IEEE 802.11: Could not add STA to kernel driver
Oct 23 15:05:27.998 DD-WRTsean daemon.notice hostapd: wlan2: STA e0:f7:2xxxx IEEE 802.11: Could not add STA to kernel driver
Oct 23 15:05:28.012 DD-WRTsean daemon.notice hostapd: wlan2: STA e0:f7:xxxxxx IEEE 802.11: Could not add STA to kernel driver
Okay, the tablet is also saying access point temporarily full...this had been working fine recently and no new devices have been added...this is when trying to connect to any remote router/vap. So secondary router 1 or router 2 both get their dhcp address from primary router and the tablet gives the same error. I check when trying to connect to both secondary and same problem on regular WAP and VAP...I checked both to make sure there was enough "space" number of devices etc ...and fine, one router only really runs about 4 devices and the other runs several. The output above is from the router that runs only 4...
So of course the primary is still running 10/4 version...and when I try to connect tablet to that...which is supplying the dhcp to the secondary...it connects just fine.
Other than that, other devices seem to connect okay including amazon like echo and such. I have just got back into town so ill play a bit more but its a strange one. I have changed nothing in configuration. An amazon tablet quirk but shown via a firmware change.
I am going to look at updating primary to 10/19 after trying to track this one down a bit better.
I "THINK" there is an issue with adding, changing wireguard tunnels
My "old" R9000 has been running the same config for about three years, has started having connectivity issues with the 6xxxx releases. Although I've only done in-place keep config upgrades since 2022 so was thinking that might be a potential cause.
Only until yesterday when the "new" R9000 behaved the same way after fiddling with tunnel settings.
Not sure where to begin looking in logs, but happy to dump them for someone smarter if they'll let me know what they want.
Since I disabled automatic reboot on my MR7350 at night shortly after release I ran into a problem yesterday.
Several WLAN devices stated "no internet" when connecting to WLAN.
After waiting for like ~20 Minutes this message went away.
Today this problem again was a thing.
Now I toggled WLAN off and on on them to be able to connect.
Looking through messages I have no idea about the reasons.
Since ipv4 lease time is 1440 minutes and radvd provided ULA prefix has default lease time (30 days I think) I decided to reduce this drastically and watch behaviour of my devices.
For IPv4 I set this to 240 minutes.
For IPv6 I added AdvValidLifetime and AdvPreferredLifetime, each for 14400 seconds (also 4 hours) in radvd conf for my ULA prefix.
Joined: 07 Jan 2025 Posts: 237 Location: Bethel Park, PA, USA
Posted: Fri Oct 24, 2025 18:19 Post subject:
dplotz wrote:
Router/Version: Linksys MR7350 x 3
File/Kernel: DD-WRT v3.0-r62374 std (10/19/25) / Linux 6.6.112-rt29 #4339 SMP Sun Oct 19 06:25:12 +07 2025 aarch64
Previous/Reset: DD-WRT v3.0-r62365 std (10/17/25), last reset at r62365
Mode/Status: Gateway (NSS-ECM), Access Point (2.4GHz-HT20 N/G Mixed, 5GHZ-HT80 AC/N 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:
After update, went into a a boot loop. It would come up for about 1 minute, just long enough for the GUI to start, then crash and restart. I've included a syslog excerpt that shows several crash/reboots. Hope it helps.
Thank you Brainslayer.
At the suggestion of @CherAlban, I'm trying this version again with a fresh config. At the moment, I'm at a very minimal configuration - no VPNs, no VAPs, no IPv6, no SmartDNS and default SFE rather than NSS-ECM. I will start enabling features over the next few days and try to determine what in my configuration makes it unstable. It's been up and stable for about 2 hours now. _________________ Formerly dpp3530 Linksys MR7350
Gateway, 2 wired APs, NSS-ECM , Clock 1440MHz
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: 237 Location: Bethel Park, PA, USA
Posted: Sun Oct 26, 2025 2:03 Post subject:
None of my devices could connect to wifi on either the 2.4 or 5GHz. Windows couldn't even see the SSIDs. Same issue on two devices. Upgraded to r62418, wiped it, and started over. Updates in that thread. _________________ Formerly dpp3530 Linksys MR7350
Gateway, 2 wired APs, NSS-ECM , Clock 1440MHz
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
Router/Version: Asus rt-ax89x rev.B2
File/Kernel: DD-WRT r62374
Previous/Reset: 62192\Yes (erase nvram via telnet)
Mode/Status: AP, NSS-ECM-SFE, PANAMA domain, Advanced Settings manual 36 dBm on both radios, but show only 30dBm in GUI.
Issues/Errors: Yes. Nothing changes for me from build 61238. In this case this builds not usable for me. Also in this build added issue with not stable 2,4ghz at all, - repeated disconections and a lot of repeated code in log:
Code:
Oct 19 22:17:49.096 DD-WRT user.err : [ath11k_watchdog] : zero signal issue detected on interface wlan1
have you tried to turn off NSS-ECM-SFE
al_bo wrote:
My setup is almost basic.
what is basic...have you tried any other domain than Panama....try Costa Rica
or another...TX power depends on country domains...
also 36 dBm is stupid and wont work on Panama...even 30dBm is too much and this means devices need to be able to support it..so, not always 30 is good..but anyway...it should work...
al_bo wrote:
I found in GUI after build from 61238, that MAC address 2,4Ghz and 5Ghz are the same in wireless tab
yep mine are the same too, but i don't have client connection issues...so, you have to consider another options and issues...tightly related to your hardware or set up may be...or bad client incompatibility..and so...
at the end of the day the only thing that will help to address and tackle the problem, will be serial output...settings used and ect... all available details that will help the main developer and others to look at and spot an issue/s...
I just posted issues if it not works like before in a previous builds. I use my the same setup a lot of years in DD-WRT.
I have tried to turn off NSS-ECM-SFE, but there is no any difference.
I have no skills to make logs from serial, but time to time I am post logs from GUI.
I have tried all builds till today, till build 62778, but issue with not visible 2,4 when connected to 5ghz still persist on my samsung s24.
In some post I found to some codes that I can try to use in telnet described here https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1318458#1318458:
