Routers: TP-Link TL-WR841ND v7.1, v7.2
Upgrade: via web
Firmware: v3.0-r41813 std (12/29/19)
Kernel: Linux 3.10.108-d8 #32507 Sun Dec 29 11:29:13 +04 2019 mips
Previous: 37961
Mode: Access Point
Reset: No
Errors: when router is idle, the 'Free Memory' will
decrease continuously resulting auto-reboot.
if any network activities before auto-reboot, the amount of
free memory will increase to normal level.
no memory leak when wireless disabled (radio off).
nvram erase / reset to default settings reconfig
I had done this with several builds after 37961, did not help.
to be sure, expressly do it again with this build, same problem.
There must be some memory leaks after build 37961, it is too late to
track back which modification that caused it.
ahhh I've tried all the builds since 12/10 and they have all had the same WiFi problem. Thinking maybe of purchasing a replacement router, any suggestions from you kind folks?
I've had my R9000 for about a month now and the WiFi is excellent. The whole router is great. _________________ Netgear R9000
DD-WRT v3.0-r55819 std (04/17/24)
Linux 4.9.337 #722 SMP Wed Apr 17 04:16:49 +07 2024 armv7l
Gateway, AP, DNSMasq, Clock 2000MHz
VAP on wlan1 for internet devices
IPv4 & IPv6 (Prefix Delegation)
Static Leases & DHCP
CloudFlare, no SFE, SmartDNS, no QoS
2.4GHz: Vanilla, Airtime Fairness, NG-Mixed, ACK Timing 3150, WPA2 w/AES & WPA3
5GHz: Vanilla, Airtime Fairness, AC/N Mixed, ACK Timing 3150, WPA2 w/AES & WPA3
2 Netgear AX1800 WiFi Mesh Extenders
Xfinity 1.2Gbps/35Mbps
Joined: 14 Sep 2019 Posts: 301 Location: Maine, USA
Posted: Thu Jan 02, 2020 14:47 Post subject:
Router/Version: TP-Link ARCHER-C7 v4
File: tplink_archer-c7-v4.bin
Firmware: DD-WRT v3.0-r41813 std (12/29/19)
Kernel: Linux 3.18.140-d1 #63989 Sun Dec 29 12:06:59 +04 2019 mips
Mode: Router/USB/MAC based QOS FQ_CODEL_FAST
Previous: r41418
Reset?: N
Status: Working
Router/Version: TP-Link ARCHER-C7 v4
File: tplink_archer-c7-v4.bin
Firmware: DD-WRT v3.0-r41813 std (12/29/19)
Kernel: Linux 3.18.140-d1 #63989 Sun Dec 29 12:06:59 +04 2019 mips
Mode: AP
Previous: r41418
Reset?: N
Status: Working
ahhh I've tried all the builds since 12/10 and they have all had the same WiFi problem. Thinking maybe of purchasing a replacement router, any suggestions from you kind folks?
I've had my R9000 for about a month now and the WiFi is excellent. The whole router is great.
Router: 2x Netgear R7800 (Gateway Router & AP Router)
Firmware: DD-WRT v3.0-r41813 std (12/29/19) [from: DD-WRT v3.0-r39855M kongat (05/25/19)]
Linux Rel: Linux 4.9.207 #502 SMP Sun Dec 22 [from: Linux 4.9.177 #412 SMP Sat May 25]
Reset: YES [nvram erase && reboot also manually configured]
Status & Uptime: Working since installed 2020-JAN-02, Over 29 hours uptime because of tweaking configuration
Thank You BrainSlayer for your Great Work with DDWRT! _________________ Home Network on Telus 1Gb PureFibre - 10GbE Copper Backbone
2x R7800 - Gateway & WiFi & 3xWireGuard - DDWRT r53562 Std k4.9
Off Site 1
R7000 - Gateway & WiFi & WireGuard - DDWRT r54517 Std
E3000 - Station Bridge - DDWRT r49626 Mega K4.4
Off Site 2
R7000 - Gateway & WiFi - DDWRT r54517 Std
E2000 - Wired ISP IPTV PVR Blocker - DDWRT r35531
When the USB 2.0 hub connected to the router experiences infrequent random disconnection, the process manager kills all NAS services. When the hub gets automatically re-detected, the process manager does not restart the NAS services.
Workaround:
Code:
# for s in lighttpd samba3 ftpsrv dlna; do startservice $s ; done
wenzhuo wrote:
* Router Model: Netgear WNDR4300
* Firmware Version: DD-WRT v3.0-r41813 std (c) 2019 NewMedia-NET GmbH
* Kernel Version: Linux DD-WRT 3.18.140-d1 #64007 Sun Dec 29 12:32:33 +04 2019 mips DD-WRT
* Upgraded from: DD-WRT v3.0-r41586
* Reset: No. Just webflash.
* Features enabled: NAS services, OpenVPN Server, WireGuard, openvpn client instances started using a wanup script, and VLANs configured in rc_startup
* Status: Up and running for 20 hours
* Errors
1. VPN clients are blocked by the recent CVE-2019-14899 mitigation
Quote:
```
root@DD-WRT:~# iptables -t raw -nvL PREROUTING
Chain PREROUTING (policy ACCEPT 53545 packets, 9715K bytes)
pkts bytes target prot opt in out source destination
653 55473 DROP 0 -- !oet1 * 0.0.0.0/0 172.16.12.0/24 ADDRTYPE match src-type !LOCAL
398 69076 DROP 0 -- !tun2 * 0.0.0.0/0 172.16.10.208/28
```
* Workarounds
Quote:
```
root@DD-WRT:~# nvram show | grep _mit
oet1_mit=1
size: 55900 bytes (9636 left)
openvpncl_mit=1
openvpn_mit=1
root@DD-WRT:~# nvram set oet1_mit=0
root@DD-WRT:~# nvram set openvpncl_mit=0
root@DD-WRT:~# nvram set openvpn_mit=0
root@DD-WRT:~# nvram commit
root@DD-WRT:~# nvram show | grep _mit
oet1_mit=0
size: 55900 bytes (9636 left)
openvpncl_mit=0
openvpn_mit=0
root@DD-WRT:~#
```
If you assign a gateway on the Setup->Basic Setup page under Network setup, it will work last I knew. Why add lines to dnsmasq custom config that aren't necessary. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
That only applies to where the router itself as a device goes for next hop (such as getting a ntp query or an dns lookup). This is for the gateway that the DDWRT router assigns to it's DHCP clients. It is a supported config and we updated the Wiki last time with the new protocol:
https://wiki.dd-wrt.com/wiki/index.php/DNSMasq_as_DHCP_server#Assign_an_alternate_Gateway
This is for the situation when the DDWRT router is acting as a DNS/CHPS server only running DNSMasq with no WAN side connection. Thus, it needs to hand out a different gateway.
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Tue Jan 14, 2020 22:55 Post subject:
malbers15 wrote:
Hi kernel-panic69,
That only applies to where the router itself as a device goes for next hop (such as getting a ntp query or an dns lookup). This is for the gateway that the DDWRT router assigns to it's DHCP clients. It is a supported config and we updated the Wiki last time with the new protocol:
https://wiki.dd-wrt.com/wiki/index.php/DNSMasq_as_DHCP_server#Assign_an_alternate_Gateway
This is for the situation when the DDWRT router is acting as a DNS/CHPS server only running DNSMasq with no WAN side connection. Thus, it needs to hand out a different gateway.
I have re-verified on this build with a fresh re-install and you are correct; false alarm on my part. I may have needed to wipe my settings before and do a reset to defaults to clear bad data. Sorry and all is well with the alternative gateway assignment functionality on r41813!
I've tried all the builds since 12/10 and they have all had the same WiFi problem. Thinking maybe of purchasing a replacement router, any suggestions from you kind folks?
