WARNING: This thread is to report on flashing this experimental test build, providing important info for both developers and users. Always state your hardware model, version, mode..
If you don't understand the risks or what to flash and how, with a means of recovery if it bricks, do NOT flash this experimental test build. _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 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 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 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
WNDR3700 V4
DD-WRT v3.0-r39101 std (03/07/19)
Linux 3.18.136 #35189 Thu Mar 7 03:54:27 CET 2019 mips
switch / ovpn server / samba share ext4
ovpn is still 2.4.6 but she works ok with ovpn client 2.4.7 on me phone
Only problem is it shows crazy-ass CPU load
Here is some 'more log stuff' iffin you want to see.
###
EA8500
r39101 'dd-wrt-webupgrade.bin' is 42336256 bytes so he still won't work
Joined: 30 Jun 2014 Posts: 59 Location: California
Posted: Thu Mar 07, 2019 20:48 Post subject:
Netgear WNDR3700 V4
DD-WRT v3.0-r39101 std (03/07/19)
Linux 3.18.136 #35189 Thu Mar 7 03:54:27 CET 2019 mips
Update via GUI from r38840 with no reset
Haven't been running very long, but not experiencing the 100% CPU issue.
root@WNDR3700v4_Base:~# uptime
12:46:48 up 2:42, load average: 0.07, 0.05, 0.00
Netgear WNDR3700 v2
DD-WRT v3.0-r39101 std (03/07/19)
Linux 3.10.108-d8 #4248 Thu Mar 7 03:51:38 CET 2019 mips
Update via GUI from r38840 with no reset
Even less running time here, but still no CPU usage problem.
root@WNDR3700v2:~# uptime
16:56:44 up 56 min, load average: 0.09, 0.15, 0.13
Router Model TP-Link TL-WR841ND v11
Firmware Version DD-WRT v3.0-r39101 std (03/07/19)
Kernel Version Linux 3.18.136 #35151 Thu Mar 7 03:01:54 CET 2019 mips
Uptime 2:36
Load Average 0.06, 0.01, 0.00
Update from 39081 via telnet
Reset: no
Status: Working OK as AP, NG-Mixed, HT40, QOS
Problems: none
Better throughput than previous firmware.
More free memory (~34-35% vs ~23-25%), back how it was a couple of months ago.
Joined: 30 Jun 2014 Posts: 59 Location: California
Posted: Thu Mar 07, 2019 23:04 Post subject:
bushant wrote:
WNDR3700 V4
CPU load started hi ~90%. Slowly dropped to ~1%. Remains low.
Soon after I posted with "no problems here," the CPU usage (as shown by uptime) on the WNDR3700 v2 jumped to more than 5... as in 500% Certainly there is something wrong with that number, but the router response was quite sluggish so it was busy with something. Top and ps did not show what was consuming the CPU.
Like Bushant, I also noticed the usage number slowly dropping over the next hour as the router response improved. I am guessing that there was a serious spike in the calculated CPU load (perhaps a divide by zero??). A huge but short duration number combined with a long averaging window would produce this behavior.
WNDR3700v4 r39101
up 1:38
Load Average 0.00, 0.00, 0.00
connected to its ovpn server w/phone and run couple speed tests
went right up to 80% but now she went back to --
up 1:44
0.14, 0.18, 0.08
Not sure WTH was going on after the install but she seems to be doing ok better now after I rebooted her
####
EDIT:
still holding normal CPU/load av... now uptime 14:48
Last edited by mrjcd on Fri Mar 08, 2019 12:43; edited 1 time in total
Router Name
DD-WRT-615
Router Model
D-Link DIR-615-I1
Firmware Version
DD-WRT v3.0-r39101 std (03/07/19)
Kernel Version
Linux 3.10.108-d8 #4206 Thu Mar 7 02:25:29 CET 2019 mips
Router Model:
Status:
Reset: None
Errors:
Flash DD-WRT upgrade from web. OK
WARNING: This thread is to report on flashing this experimental test build, providing important info for both developers and users. Always state your hardware model, version, mode..
If you don't understand the risks or what to flash and how, with a means of recovery if it bricks, do NOT flash this experimental test build.
Many of us really appreciate your testing, report, and tracking efforts. If I might make one small suggestion in the spirit of copy and paste?
It would be very helpful if the ticket links included a subject or summary so we could quickly see the score card of what the problem issues are without having to click into and remember each ticket number.