Router ModelNetgear R7500v2
Firmware Version DD-WRT v3.0-r34900M kongat (02/12/18 )
Kernel VersionLinux 3.18.94 #267 SMP PREEMPT Mon Feb 12 00:09:00 CET 2018
Running 1hr uptime. CPU Temperature seems fixed but the ath temps look strange... used to be 23-25dC, now upper 60dC:
CPU 59.0 °C / ath0 61 °C / ath1 61 °C
Joined: 30 Jan 2015 Posts: 676 Location: Texas, USA
Posted: Tue Feb 13, 2018 0:10 Post subject:
jerrytouille wrote:
Router ModelNetgear R7500v2
Firmware Version DD-WRT v3.0-r34900M kongat (02/12/18 )
Kernel VersionLinux 3.18.94 #267 SMP PREEMPT Mon Feb 12 00:09:00 CET 2018
Running 1hr uptime. CPU Temperature seems fixed but the ath temps look strange... used to be 23-25dC, now upper 60dC:
CPU 59.0 °C / ath0 61 °C / ath1 61 °C
I see 10degC less: DD-WRT v3.0-r34900M kongat (02/12/18 )
CPU TemperatureCPU 50.0 °C / ath0 51 °C / ath1 51 °C
I'm in Texas. _________________ ASUS GT-BE98 PRO Main: Fiber 5gbps up/down
ASUS AXE16000: AI Mesh node
2 X ASUS RT-AX89X: AI Mesh nodes
QNAP QSW-1208-8C 12-Port 10GbE Switch
XS712T ProSafe 12-Port 10GbE Switch
3 X R9000 DD-WRT Mesh
Router ModelNetgear R7500v2
Firmware Version DD-WRT v3.0-r34900M kongat (02/12/18 )
Kernel VersionLinux 3.18.94 #267 SMP PREEMPT Mon Feb 12 00:09:00 CET 2018
Running 1hr uptime. CPU Temperature seems fixed but the ath temps look strange... used to be 23-25dC, now upper 60dC:
CPU 59.0 °C / ath0 61 °C / ath1 61 °C
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Tue Feb 13, 2018 2:33 Post subject:
<Kong> wrote:
jerrytouille wrote:
Router ModelNetgear R7500v2
Firmware Version DD-WRT v3.0-r34900M kongat (02/12/18 )
Kernel VersionLinux 3.18.94 #267 SMP PREEMPT Mon Feb 12 00:09:00 CET 2018
Running 1hr uptime. CPU Temperature seems fixed but the ath temps look strange... used to be 23-25dC, now upper 60dC:
CPU 59.0 °C / ath0 61 °C / ath1 61 °C
They weren't correct in earlier builds.
so all this time they were wrong? i figured one of them was wrong (idle 19c in a 21c room, but the other radio looked ok @ 30c or so). now they seem to be nearly sync'd to cpu temp.
What should the R7800 cpu clock read? Mine is reading 800MHz/800MHz. Is that status reading dynamic or fixed? (Meaning does it adjust up and down based on load/speed, or is it showing static max cpu clock capability?)
If it is max cpu clock, then I don’t think that is right on my R7800?
Joined: 30 Jan 2015 Posts: 676 Location: Texas, USA
Posted: Tue Feb 13, 2018 5:10 Post subject:
Siggyceline wrote:
Also...quick noob question:
What should the R7800 cpu clock read? Mine is reading 800MHz/800MHz. Is that status reading dynamic or fixed? (Meaning does it adjust up and down based on load/speed, or is it showing static max cpu clock capability?)
If it is max cpu clock, then I don’t think that is right on my R7800?
Thanks for any feedback!
Yes, yours is dynamic.
To set the peak/max fixed, you have to use Tatsuya's startup script:
for CPUFREQ in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do [ -f $CPUFREQ ] || continue; echo -n performance > $CPUFREQ; done _________________ ASUS GT-BE98 PRO Main: Fiber 5gbps up/down
ASUS AXE16000: AI Mesh node
2 X ASUS RT-AX89X: AI Mesh nodes
QNAP QSW-1208-8C 12-Port 10GbE Switch
XS712T ProSafe 12-Port 10GbE Switch
3 X R9000 DD-WRT Mesh
What should the R7800 cpu clock read? Mine is reading 800MHz/800MHz. Is that status reading dynamic or fixed? (Meaning does it adjust up and down based on load/speed, or is it showing static max cpu clock capability?)
If it is max cpu clock, then I don’t think that is right on my R7800?
Thanks for any feedback!
Yes, yours is dynamic.
To set the peak/max fixed, you have to use Tatsuya's startup script:
for CPUFREQ in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do [ -f $CPUFREQ ] || continue; echo -n performance > $CPUFREQ; done
Joined: 16 Nov 2015 Posts: 6440 Location: UK, London, just across the river..
Posted: Tue Feb 13, 2018 6:46 Post subject:
Router Model Netgear R7800
Firmware Version DD-WRT v3.0-r34900M kongat (02/12/1
Kernel Version Linux 3.18.94 #267 SMP PREEMPT Mon Feb 12 00:09:00 CET 2018 armv7l
update: via ddup
reset : NO
status: operational
errors:
Jan 1 02:00:34 R7800 daemon.err ntpclient[2321]: Failed resolving address to hostname 2.pool.ntp.org: Try again
Jan 1 02:00:34 R7800 daemon.err ntpclient[2321]: Failed resolving server 2.pool.ntp.org: Network is down
Jan 1 02:00:34 R7800 daemon.notice ntpclient[2321]: Network up, resolved address to hostname 212.18.3.19
Jan 1 02:00:34 R7800 daemon.debug ntpclient[2321]: Connecting to 212.18.3.19 [212.18.3.19] ...
Feb 13 08:30:19 R7800 daemon.info ntpclient[2321]: Time set from 212.18.3.19 [212.18.3.19].
Feb 13 08:30:19 R7800 daemon.err process_monitor[2320]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
so NTP time is kind of working now
Feb 13 08:32:17 R7800 user.info : Authentication fail
Feb 13 08:32:23 R7800 user.info : httpd login failure - bad passwd ! --- but i was logged in with correct pass ???!!! _________________ 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
Router Model Netgear R7800
Firmware Version DD-WRT v3.0-r34900M kongat (02/12/1
Kernel Version Linux 3.18.94 #267 SMP PREEMPT Mon Feb 12 00:09:00 CET 2018 armv7l
update: via ddup
reset : NO
status: operational
errors:
Jan 1 02:00:34 R7800 daemon.err ntpclient[2321]: Failed resolving address to hostname 2.pool.ntp.org: Try again
Jan 1 02:00:34 R7800 daemon.err ntpclient[2321]: Failed resolving server 2.pool.ntp.org: Network is down
Jan 1 02:00:34 R7800 daemon.notice ntpclient[2321]: Network up, resolved address to hostname 212.18.3.19
Jan 1 02:00:34 R7800 daemon.debug ntpclient[2321]: Connecting to 212.18.3.19 [212.18.3.19] ...
Feb 13 08:30:19 R7800 daemon.info ntpclient[2321]: Time set from 212.18.3.19 [212.18.3.19].
Feb 13 08:30:19 R7800 daemon.err process_monitor[2320]: cyclic NTP Update success (servers 2.pool.ntp.org 212.18.3.19 88.99.174.22)
so NTP time is kind of working now
Feb 13 08:32:17 R7800 user.info : Authentication fail
Feb 13 08:32:23 R7800 user.info : httpd login failure - bad passwd ! --- but i was logged in with correct pass ???!!!
in my log is highlighted in red. I assume that's because it's from the daemon.err process monitor...because the content of the message is "success", not a "failure". Anyways, I'm back on r33770M again. I find red highlighting of success messages in the log too distracting from the events that I really need to see *smile*.