Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Tue May 12, 2020 17:21 Post subject:
The reason why I recommended 37961 somewhat across the board for TL-WR* 4MB devices in the other thread is it is post commits that fix certain issues on these devices and a known overall working build from looking through several threads on here. There may be newer builds that work okay, but that is from a ton of reading trying to pick apart the monstrosity messes people have made of "device threads". _________________ "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
The reason why I recommended 37961 somewhat across the board for TL-WR* 4MB devices in the other thread is it is post commits that fix certain issues on these devices and a known overall working build from looking through several threads on here....
hmm can i define "better"...
better GUI access, https support as well some new fixes...you can have a look on SVN if you follow it......
How’d you get HTTPS working on your 740? Was pretty sure no OpenSSL on 4mb devices...
I have a 740N v4 and I’ve been upgrading to the latest builds without any issues, for whatever a single data point is worth. Like another poster said, this is a new lease on life for a device I was going to recycle otherwise (had gotten quite unstable with TP-Link firmware)
How’d you get HTTPS working on your 740? Was pretty sure no OpenSSL on 4mb devices...
...
https support on the GUI is broken on my 4M flash device for a long time, but SSH is working ...
Edit : https GUI webpage did not work on r39xxx and above I have tested up to a few r41xxx builds, and I can't remember a r38xxx I have tested was working with https GUI. If someone knows the last 4M build with working https on the GUI let us know
Last edited by servicetech on Thu May 14, 2020 13:33; edited 2 times in total
Joined: 16 Nov 2015 Posts: 6447 Location: UK, London, just across the river..
Posted: Thu May 14, 2020 10:21 Post subject:
wrtf wrote:
Alozaros wrote:
hmm can i define "better"...
better GUI access, https support as well some new fixes...you can have a look on SVN if you follow it......
How’d you get HTTPS working on your 740? Was pretty sure no OpenSSL on 4mb devices...
I have a 740N v4 and I’ve been upgrading to the latest builds without any issues, for whatever a single data point is worth. Like another poster said, this is a new lease on life for a device I was going to recycle otherwise (had gotten quite unstable with TP-Link firmware)
BS was doing some changes recently, but didn't make it i guess, haven't seen https on 740 to work....
the only option to secure it it to lock down GUI via iptables rules and have SSh with key log in only than, you can turn on GUI via iptables rule and log in via GUI...if so... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
work fine, dual band working, CPU load never up more than 0.60
my longest continuous poweron = 16 days, cannot keep it more than that, cause by our occasionally black-out / no electricity in my area.
Require FULL RESET and DO NOT Restore the setting from backup (i tried restore and end up router sporadic restart and error occurs).
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Sat Jul 04, 2020 3:26 Post subject:
Alozaros wrote:
as far as WR940NDv3-v6/WR941NDv6 i don't know how the development goes this days, but my encounter with a friend WR940 series was equal to stay away from those...
I now have in my inventory a TL-WR940Nv3 running 43516. I've ran it through some hoops without tweaking anything under the hood and it's fairly stable. 43516 is the first to have some much-awaited webUI stability fixes.
Thank you for this update. Same device as WR941NDv6 except the non detachable antennas. Don`t see any "must have" in the build, except the WPA3 support. (not usable to me no WPA3 client hardware).
work fine, dual band working, CPU load never up more than 0.60
my longest continuous poweron = 16 days, cannot keep it more than that, cause by our occasionally black-out / no electricity in my area.
Require FULL RESET and DO NOT Restore the setting from backup (i tried restore and end up router sporadic restart and error occurs).
For TP-Link TL-MR3420v1 users please beware start from r42681 and up (r43800 latest that I try) I got bootlop .
latest beta r42617 was okay boot normal
hmm can i define "better"...
better GUI access, https support as well some new fixes...you can have a look on SVN if you follow it...
...
Most of the addons and fixes don't apply to these 4M flash devices WR940NDv3-v6/941NDv6 and similar as there is no openvpn, USB - Samba, wireguard, 5G and more, but they harm WLAN stability, performance, usability on these chipsets.
The r40750/r40863 are the last tested and confirmed usable to me, did not test the lastest builds, as I see no benefit, only problems if I read the posts.
End of days for this hardware is close...
Many thanks to servicetec for raising this thread for the 4M/32M routers.
I have 7 * 841nd routers of v7/8/9/11, two of them are used as nat gateway with pptp client/server enabled, others are used as wifi repeaters.
I have been looking for a stable ddwrt for these 841nds in about two years ago,
the last stable version I found was r31690, others (eg: r33006/33555/r34311/r35531/r35898) all crashed when bt/emule applications were running.
Now I can confirm happily that r40750 is very stable under heavy traffic load of bt/emule.
Below is my setting in administration tab
[management]
ip filter settings
maximum ports ---> 4096
tcp timeout ---> 300
udp timeout ---> 60
[commands]
a. startup
------------------------------
# blocking downstream ipv4-mcast to wifi
insmod ebtables
insmod ebtable_filter
insmod ebt_ip
ebtables -A FORWARD -o ath0 -p ipv4 -d 01:00:5e:00:00:00/01:00:5e:00:00:00 --ip-src ! 192.168.0.0/255.255.0.0 -j DROP
# fix uni0-3 local bridging block issue for bridge mode
#swconfig dev eth0 set reset 1
#swconfig dev eth0 set enable_vlan 1
#swconfig dev eth0 vlan 0 set ports '0 1 2 3 4'
#swconfig dev eth0 set apply
# fix uni0-3 local bridging block issue for router mode
swconfig dev eth0 set reset 1
b. custom script (workaround for wifi drop issue)
------------------------------------
#!/bin/sh
if ! iw ath0 info|grep -q channel; then
echo "reconfig wifi at "`date +'%Y-%m-%d %T %Z'` >> /var/log/messages
killall -9 hostapd
hostapd -B -P /var/run/ath0_hostapd.pid /tmp/ath0_hostap.conf
fi
ps:
please add the following line in crontab to enable custom sctipt
Posted: Thu Oct 29, 2020 7:33 Post subject: wr842nd v2 and wr841n/nd v10
for now I am using build 42514 for wr841n/nd v10. so far no problem. I still am observing the qos for mobile legend and league of legends mobile players if they are having problems with the ping. as for wr842nd v2, I am using it as an extender dhcp disabled. wr842nd with 42602 build has no problem so far.
I posted this on the new release page, but my aim was to put it here from the beginning.
Router/Version: TP-Link TL-WR940ND V6
Firmware: DD-WRT v3.0-r44538 std (10/13/20)
Kernel: Linux 3.18.140-d5 #93622 Tue Oct 13 04:44:34 +04 2020 mips
File/Upload: tl-wr940ndv6-webflash.bin / Upgrade from Web Interface
Mode: Gateway/WDS AP, Gateway/WDS Station, Router/AP
Reset: Reset to Default from Web Interface
Previous: DD-WRT v3.0-r42015 std (01/18/20)
Setup Using: Run each configuration with services recommended in wiki instructions plus NTP ssh, and syslog, minus Telnet and WAN Traffic Counter.
Status:Works excellent after Tuning for Low Memory Routers.
Tuning for Low Memory Routers (Objective: reduce memory consumption):
Setup > Basic Setup > STP disabled
Services > dnsmasq > Maximum Cached Entries 0
Services > WAN Traffic Counter disabled
Administration > IP Filter Settings > UDP Timeout (in seconds) 15
Notes:
The router was unusable before Tuning for Low Memory Routers was performed.
Symptoms before tuning:
1. High CPU consumption
2. Free memory goes to zero
3. Router crashes
Tunes That Produced the Biggest Result:
1. STP disabled
2. UDP Timeout (in seconds) 15
3. Maximum Cached Entries 0
Note: Don’t use STP if at all possible. It’s usually quite possible. STP is recommended on the Wiki.
Result:
1. No longer need to disable resetbutton
2. No longer need to disable http
3. Router works better after tuning with resetbutton and http enabled than before tuning with the services disabled. For me, tuning used to be disabling services.
Log Statistics at 15 Minute Intervals (most recent entries)
Code:
Nov 12 19:00:01 wrt0 user.notice root: UPTIME
Nov 12 19:00:01 wrt0 user.notice root: 19:00:01 up 1 day, 4:09, load average: 0.52, 0.53, 0.37
Nov 12 19:00:01 wrt0 user.notice root: FREE
Nov 12 19:00:01 wrt0 user.notice root: total used free shared buff/cache available
Nov 12 19:00:01 wrt0 user.notice root: Mem: 29416 22464 4176 0 2776 4572
Nov 12 19:00:01 wrt0 user.notice root: Swap: 0 0 0
Nov 12 19:00:01 wrt0 user.notice root: CONNECTIONS
Nov 12 19:00:01 wrt0 user.notice root: 39 tcp
Nov 12 19:00:01 wrt0 user.notice root: 94 udp
Nov 12 19:00:01 wrt0 user.notice root: _
Nov 12 19:15:02 wrt0 user.notice root: UPTIME
Nov 12 19:15:02 wrt0 user.notice root: 19:15:02 up 1 day, 4:24, load average: 1.93, 0.90, 0.58
Nov 12 19:15:02 wrt0 user.notice root: FREE
Nov 12 19:15:02 wrt0 user.notice root: total used free shared buff/cache available
Nov 12 19:15:02 wrt0 user.notice root: Mem: 29416 23132 3516 0 2768 3900
Nov 12 19:15:02 wrt0 user.notice root: Swap: 0 0 0
Nov 12 19:15:02 wrt0 user.notice root: CONNECTIONS
Nov 12 19:15:04 wrt0 user.notice root: 194 tcp
Nov 12 19:15:04 wrt0 user.notice root: 1091 udp
Nov 12 19:15:04 wrt0 user.notice root: _
Nov 12 19:30:01 wrt0 user.notice root: UPTIME
Nov 12 19:30:01 wrt0 user.notice root: 19:30:01 up 1 day, 4:39, load average: 0.03, 0.18, 0.36
Nov 12 19:30:01 wrt0 user.notice root: FREE
Nov 12 19:30:01 wrt0 user.notice root: total used free shared buff/cache available
Nov 12 19:30:01 wrt0 user.notice root: Mem: 29416 17284 8904 0 3228 9740
Nov 12 19:30:01 wrt0 user.notice root: Swap: 0 0 0
Nov 12 19:30:01 wrt0 user.notice root: CONNECTIONS
Nov 12 19:30:01 wrt0 user.notice root: 154 tcp
Nov 12 19:30:01 wrt0 user.notice root: 521 udp
Nov 12 19:30:01 wrt0 user.notice root: _
Nov 12 19:45:00 wrt0 user.notice root: UPTIME
Nov 12 19:45:00 wrt0 user.notice root: 19:45:00 up 1 day, 4:54, load average: 0.00, 0.01, 0.13
Nov 12 19:45:00 wrt0 user.notice root: FREE
Nov 12 19:45:00 wrt0 user.notice root: total used free shared buff/cache available
Nov 12 19:45:00 wrt0 user.notice root: Mem: 29416 18272 7336 0 3808 8756
Nov 12 19:45:00 wrt0 user.notice root: Swap: 0 0 0
Nov 12 19:45:00 wrt0 user.notice root: CONNECTIONS
Nov 12 19:45:00 wrt0 user.notice root: 48 tcp
Nov 12 19:45:00 wrt0 user.notice root: 71 udp
Nov 12 19:45:00 wrt0 user.notice root: _
WDS/Connection Watchdog:
After adjusting Interval (in seconds), A new script and sleep timer is spawned, leaving the original script and sleep timer running.
Here is the process list after changing it four times without a reboot.
root@wrt4:~# ps |grep "sleep\|wds" |grep -v grep
1810 root 1380 S /bin/sh /etc/config/wdswatchdog.sh
1978 root 1380 S /bin/sh /etc/config/wdswatchdog.sh
3949 root 1380 S /bin/sh /etc/config/wdswatchdog.sh
3961 root 1380 S sleep 1000
3970 root 1380 S sleep 300
4027 root 1380 S /bin/sh /etc/config/wdswatchdog.sh
4032 root 1380 S sleep 300
4037 root 1380 S sleep 1000
Disabling the reset button from Web interface does not work.
Last edited by posterlion on Sat Nov 14, 2020 15:40; edited 1 time in total