Router/Version: R7800
Previous/Reset: r61915 No reset
Mode/Status: Gateway, SFE, AP, VAPs
Issues/Errors: None, 9 hours uptime and all is working
Noticed : 2.4GHz LED works again
Second R7800
Router/Version: R7800
Previous/Reset: r57793 and reset to factory default
Mode/Status: AP, VAPs
Issues/Errors: Memory available at Satus tab not present see screenschot
A reset did not helped
Router/Version: R9000
Previous/Reset: factory to dd-wrt firmware & reset to default via button
Mode/Status: Gateway, AP
Issues/Errors: Memory available at Satus tab not present see screenschot
A reset did not helped
Router Model 3x MX4300 and gateway, wap/vap and switch, 3x as mesh wap providers
Firmware Version DD-WRT v3.0-r61970 std (07/24/25)
update: GUI
reset: NO
mode: Gateway, WAP,VAP, dhcp server, wireguard server and nordvpn client
status: only upgraded the VAP router and still has the problem with the vap deauth.. this router is what I call WAPMX
WAP/VAP router log
Code:
Jul 25 23:46:12.040 DD-WRT WAPMX daemon.info hostapd: wlan1.1: STA fc:67:1f:0d:2d:4d IEEE 802.11: deauthenticated due to local deauth request
Jul 25 23:46:20.947 DD-WRT WAPMX daemon.notice hostapd: wlan1.1: STA fc:67:1f:0d:2d:4d IEEE 802.11: did not acknowledge authentication response
Jul 25 23:47:25.943 DD-WRT WAPMX daemon.info hostapd: wlan1.1: STA fc:67:1f:0d:2d:4d IEEE 802.11: deauthenticated due to local deauth request
Jul 25 23:47:52.620 DD-WRT WAPMX daemon.notice hostapd: wlan1.1: STA fc:67:1f:0d:2d:4d IEEE 802.11: did not acknowledge authentication response
Jul 25 23:47:56.506 DD-WRT WAPMX daemon.notice hostapd: wlan1.1: STA fc:67:1f:0d:2d:4d IEEE 802.11: did not acknowledge authentication response
Jul 25 23:48:15.951 DD-WRT WAPMX daemon.notice hostapd: wlan1.1: STA fc:67:1f:0d:2d:4d IEEE 802.11: did not acknowledge authentication response
Jul 25 23:48:47.072 DD-WRT WAPMX daemon.notice hostapd: wlan1.1: STA fc:67:1f:0d:2d:4d IEEE 802.11: did not acknowledge authentication response
Jul 25 23:48:50.963 DD-WRT WAPMX daemon.notice hostapd: wlan1.1: STA fc:67:1f:0d:2d:4d IEEE 802.11: did not acknowledge authentication response
Jul 25 23:48:54.854 DD-WRT WAPMX daemon.notice hostapd: wlan1.1: STA fc:67:1f:0d:2d:4d IEEE 802.11: did not acknowledge authentication response
Jul 25 23:48:57.613 DD-WRT WAPMX daemon.info hostapd: wlan1.1: STA fc:67:1f:0d:2d:4d IEEE 802.11: deauthenticated due to local deauth request
Jul 25 23:49:43.752 DD-WRT WAPMX daemon.notice hostapd: wlan1.1: STA fc:67:1f:0d:2d:4d IEEE 802.11: did not acknowledge authentication response
Jul 25 23:49:47.647 DD-WRT WAPMX daemon.notice hostapd: wlan1.1: STA fc:67:1f:0d:2d:4d IEEE 802.11: did not acknowledge authentication response
Jul 25 23:49:55.418 DD-WRT WAPMX daemon.notice hostapd: wlan1.1: STA fc:67:1f:0d:2d:4d IEEE 802.11: did not acknowledge authentication response
Jul 25 23:50:03.208 DD-WRT WAPMX daemon.notice hostapd: wlan1.1: STA fc:67:1f:0d:2d:4d IEEE 802.11: did not acknowledge authentication response
Jul 25 23:50:48.749 DD-WRT WAPMX daemon.info hostapd: wlan1.1: STA fc:67:1f:0d:2d:4d IEEE 802.11: deauthenticated due to local deauth request
Seems to be worse now than last version 7/14/25. Has not been installed long enough to see if it fails at approx 2 days point yet.
Not that it matters much but I did notice that the same log info is repeated on the main router, which is bridged so it is reflected on the main router log but it reports it as wlan1 instead of wlan 1.1.
So the main router, which the VAP stuff is not connected to/does not have any current vap (other than the VAP from WAPMX is bridged to it) running is reporting the connections to the VAP router, but reporting them as wlan1 instead of 1.1. I doubt it matters, but just wanted to note it in case it does happen to matter
MAIN router log
Code:
Jul 25 23:31:17.229 DD-WRTsean daemon.notice hostapd: wlan1: STA fc:67:1f:0d:2d:4d IEEE 802.11: did not acknowledge authentication response
Jul 25 23:31:21.116 DD-WRTsean daemon.notice hostapd: wlan1: STA fc:67:1f:0d:2d:4d IEEE 802.11: did not acknowledge authentication response
Jul 25 23:31:24.999 DD-WRTsean daemon.notice hostapd: wlan1: STA fc:67:1f:0d:2d:4d IEEE 802.11: did not acknowledge authentication response
Jul 25 23:31:40.565 DD-WRTsean daemon.notice hostapd: wlan1: STA fc:67:1f:0d:2d:4d IEEE 802.11: did not acknowledge authentication response
Jul 25 23:31:56.122 DD-WRTsean daemon.notice hostapd: wlan1: STA fc:67:1f:0d:2d:4d IEEE 802.11: did not acknowledge authentication response
Jul 25 23:32:00.003 DD-WRTsean daemon.notice hostapd: wlan1: STA fc:67:1f:0d:2d:4d IEEE 802.11: did not acknowledge authentication response
Jul 25 23:32:11.679 DD-WRTsean daemon.notice hostapd: wlan1: STA fc:67:1f:0d:2d:4d IEEE 802.11: did not acknowledge authentication response
Jul 25 23:32:14.440 DD-WRTsean daemon.info hostapd: wlan1: STA fc:67:1f:0d:2d:4d IEEE 802.11: deauthenticated due to local deauth request
Joined: 15 Aug 2016 Posts: 291 Location: Melbourne, Australia
Posted: Sat Jul 26, 2025 8:05 Post subject:
Vaako wrote:
Router/Version: R9000
Issues/Errors: Memory available at Status tab not present see screenshot
A reset did not helped
Mine shows up properly.
Memory Band PIc.png
Description:
Filesize:
144.46 KB
Viewed:
2768 Time(s)
_________________ Life is a journey; travel alone makes it less enjoyable and lonely.
___________________________________________________
2x Netgear R9000 & 2x XR700 Features:
- Gateway
- Overclocked -2000MHz
- SmartDNS, DDNS
- Both 5GHz & 2.4GHz using DDWRT (not Vanilla component)
- Private Home network on default br0 bridge together with vlan1 + wlan0 & 1
- Isolated port-based VLANS, placed on bridges + vAPs (wlan0.1 & 1.1) for guests & IoT devs)
- WireGuard Server for secure on-the-road access & remote control of devices @home
- OpenVPN Client for incognito & o/seas based programs
- 10G SFP+ connected to RB5009 (via optical fiber)
- QoS - HFSC/FQ_CODEL deployed on ISP's 500/50mbps connection
Joined: 16 Nov 2015 Posts: 7383 Location: UK, London, just across the river..
Posted: Sat Jul 26, 2025 9:30 Post subject:
Router Model Netgear XR500
Firmware Version DD-WRT v3.0-r61970 std (07/24/25)
Kernel Version Linux 6.1.146-rt28 #599 SMP Wed Jul 23 03:43:04 +07 2025 armv7l
Router Model TP-Link WR1043ND V2
Firmware Version DD-WRT v3.0-r61970 std (07/24/25)
Kernel Version Linux 3.18.140-d6 #244924 Thu Jul 24 07:33:15 +07 2025 mips
Router Model Netgear R7800
Firmware Version DD-WRT v3.0-r61970 std (07/24/25)
Kernel Version Linux 6.1.146-rt28 #599 SMP Wed Jul 23 03:43:04 +07 2025 armv7l
Router Model Dynalink DL-WRX36
Firmware Version DD-WRT v3.0-r61970 std (07/24/25)
Kernel Version Linux 6.6.99-rt29 #3775 SMP Wed Jul 23 07:04:30 +07 2025 aarch64
update: CLI
reset: NO
mode: Gateway/40 HT 2.4Ghz only(Vanilla)
status: Operational 10h+
errors: apart of the problem with DL-WRX36, that requires to enable SFE=3 and NSS subsystem in order to operate, get NTP time and ect....the others are fine nothing found yet..all running smooth, just 1043v2 has low free ram, but doesn't drop bellow 5MB...and GUI is sluggish kind of, but operational...will add more later...so far no problems with SmartDNS, nor visual stuff in GUI as others reported... _________________ Atheros
TP-Link WR1043NDv2 -DD-WRT 66272 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPNCli
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear R7800 -OpenWRT Kong 25.12
Netgear XR500 -DD-WRT 66280 GTW/SmDNS-Quic,AD-Blk,Forced DNS,AP&Net Isolation,x2VLAN,Vanilla
Netgear R7800 --DD-WRT r66280 Gateway/DNSCryptv2,AD-Block,Forced DNS,AP&Net Isolation,x4VLAN,IPset Firewall,Vanilla,VPN cli
Netgear R9000 --DD-WRT 66280 Gateway/SmDNS-Quic,AD-Block,AP Isolation,Firewall,Forced DNS,Vanilla
Dynalink DL-WRX36-DDWRT 66272
Broadcom
Netgear R7000 --DD-WRT 66272 GTW/DNScrypt-proxy2/AD-Block,IPset Firewall,Forced DNS,x4VLAN,VPN cli
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Joined: 21 Aug 2019 Posts: 263 Location: Here, There And Everywhere
Posted: Sun Jul 27, 2025 10:41 Post subject:
Router/Version: Netgear XR500
File/Kernel: DD-WRT v3.0-r61970 std (07/24/25) / Linux 6.1.146-rt28 #599 SMP Wed Jul 23 03:43:04 +07 2025 armv7l
Previous/Reset: r61954 / No
Mode/Status: Access point, VLAN, WDS AP
Issues/Errors: A small VLAN/WDS problem, which was present in r61954 and likely before. When a WDS station disconnects and after some time reconnects, its interface (wlan1.sta1 in my case) first disappears and then is added to the bridge br0, but not to vlan 1 (it does not appear in bridge vlan show). I have to manually execute:
Code:
bridge vlan add vid 1 dev wlan1.sta1 pvid untagged
although this same filter is already specified in Networking->Bridge VLAN Filtering. For now, my workaround is to execute this command with cron:
Code:
* * * * * root /bin/sh -c 'for iface in $(ifconfig | grep -o "wlan[0-9]\.sta[0-9]"); do bridge vlan show | grep -q "$iface" || bridge vlan add vid 1 dev "$iface" pvid untagged; done'
A better solution should probably be discussed elsewhere (Advanced networking).
Twice now with this build, I've had smartdns stop working. DNS calls hang. Retarting smartdns works and services return. Is there an issue with smartdns or do I have a bad setting? Does this sound familiar to anyone?
I haven't upgraded past build 61848 yet on my MX4300, but I see a similar problem with SmartDNS on that build. From what I can tell looking at the system log, SmartDNS starts before NTP sets the system time to a valid time. I have SmartDNS configured with only "server-tls" and "-tls-host-verify" options, and it seems -tls-host-verify fails if the system time is not set. Older builds of SmartDNS would recover automatically after NTP set the time, but the newer builds often just hang and need to be restarted.
Other than removing -tls-host-verify, another workaround would be to add "sleep 30; service smartdns restart" to the Startup script under Adminstration->Commands, assuming NTP sets the time within 30 seconds.
Joined: 04 Dec 2007 Posts: 1326 Location: Murrysville, PA
Posted: Wed Jul 30, 2025 12:59 Post subject:
BumRap wrote:
MLandi wrote:
Twice now with this build, I've had smartdns stop working. DNS calls hang. Retarting smartdns works and services return. Is there an issue with smartdns or do I have a bad setting? Does this sound familiar to anyone?
I haven't upgraded past build 61848 yet on my MX4300, but I see a similar problem with SmartDNS on that build. From what I can tell looking at the system log, SmartDNS starts before NTP sets the system time to a valid time. I have SmartDNS configured with only "server-tls" and "-tls-host-verify" options, and it seems -tls-host-verify fails if the system time is not set. Older builds of SmartDNS would recover automatically after NTP set the time, but the newer builds often just hang and need to be restarted.
Other than removing -tls-host-verify, another workaround would be to add "sleep 30; service smartdns restart" to the Startup script under Adminstration->Commands, assuming NTP sets the time within 30 seconds.
Thanks. The latest firmware seems to have this fixed (I hope). Up 24+ hours and the issue has not shown _________________ Linksys MX8500 DD-WRT v3.0-r66325 std (10/06/26)
Linux 6.12.112 #767 SMP Tue Oct 6 03:56:39 +06 2026 aarch64 Gateway, AP, DNSMasq, no ARPd caching, SmartDNS, quic, NSS-ECM, QCA NSS, no STP, IPv4 & IPv6
VAP on wlan1 for internet devices
Static Leases & DHCP
Quad9, Forced DNS, Forced DoT, QoS HFSC
2.4GHz: AP, AX Only, ACK Timing 0, WPA2 & WPA3 w/AES & GCMP
5GHz: AP, AX Only, ACK Timing 0, WPA3 w/GCMP
Netgear AX1800 WiFi Mesh Extender
Xfinity 1.2Gbps/40Mbps
.