I did first install on test router and found nothing bad
then
Installed on main router over r33555
unbound no worky -- no surprise there
no loopback on ftp
top light out
all else seems good
local DNS ok
ovpn server ok -- local DNS via ovpn ser ok
Standard static DNS ok
DNSCrypt + DNSSEC ok
port forwards good ok
QOS ok
USB SAMBA share ok
DHCP on two networks ok
39 static leases mostly split between both networks --all ok
VLAN on 1 port ok
yea the two chromycast are alive & well both on ath0.1
I clicked apply setting on 'bout every page with few minor changes and nothing broke so you can probably install over
whatever current confg you have. For best results with this a reset manual config might be best but who has the time ????
Done a reboot after messin around just to have a clean log ----
gonna let it run for a while even though no local loopback on the ftp is really buggy me
----------
Just as a note:
BS r34178 Linux 4.14.8 was a wreck. i actually installed on main router last night just see what would happen.
port forwards never worked.
unbound hang -- turned off.
had DNS for short time with stardard static but lost it.
Lost WAN and never could reaquire.
most any page would lockup router when applied settings
so there we are ---- Merry Christmas
Just installed it on my tester, top LED still missing and looks like the scaling fix is gone but both cores are showing up in the status and are working independently. I just happened to capture the screen shot when idle but did see one bounce to 600mhz. Nice touch Kong
Joined: 30 Jan 2015 Posts: 677 Location: Texas, USA
Posted: Sat Dec 23, 2017 7:20 Post subject:
I'm using this build on my R7800 setup as client bridge.
Router Model: Netgear R7800
Firmware Version DD-WRT v3.0-r34175M kongat (12/22/17)
Kernel Version Linux 4.14.8 #5 SMP PREEMPT Thu Dec 21 22:40:47 CET 2017 armv7l _________________ 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
EA8500
up 1 day 59 min
tis all worky fine on main router.
I just don't know WTH causes this:
Dec 22 15:56:43 ~ kern.warn kernel: [24765.285980] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Dec 22 15:56:43 ~ kern.warn kernel: [24765.286033] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Dec 22 15:56:43 ~ kern.warn kernel: [24765.293176] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Dec 22 15:56:43 ~ kern.warn kernel: [24765.301393] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
It's random and somewhat rare ... not like the unknown event (BTW it has not shown yet but usually takes
him more than a day ... or maybe Kong suppressed it)
The 'tx_fetch_ind event: in push mode' is not a K4.x thing. It's been around since update ath10k firmware several months back.
All google says is mostly related to the fretgear's 9984 but that is bull cause it's also been on the 9980 for long time.
----------
been playin some on the test router and yea both CPU will scale up/down just fine even though
the boot log bitches some ...
[ 2.862740] /cpus/cpu@0: unsupported enable-method property: qcom,kpss-acc-v1
[ 2.863016] CPUidle arm: CPU 0 failed to init idle CPU ops
:
[ 3.000722] trying to register driver cpufreq-dt
[ 3.003019] of: dev_pm_opp_of_cpumask_add_table: couldn't find opp table for cpu:0, -19
[ 3.008052] of: dev_pm_opp_of_cpumask_add_table: couldn't find opp table for cpu:1, -19
...this is new uglies with K4.9 but she levels herself out in the end so it's all good.
Joined: 16 Nov 2015 Posts: 7391 Location: UK, London, just across the river..
Posted: Sun Dec 24, 2017 8:37 Post subject:
Router Model Netgear R7800
Firmware Version DD-WRT v3.0-r34175M kongat (12/22/17)
Kernel Version Linux 4.14.8 #5 SMP PREEMPT Thu Dec 21 22:40:47 CET 2017 armv7l
update: 34115 >34175 via ddup
reset: no
status: operational
errors: none _________________ 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 66325 GTW/SmDNS-Quic,AD-Blk,Forced DNS,AP&Net Isolation,x2VLAN,Vanilla
Netgear R7800 --DD-WRT r66325 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 66325
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
This update "broken" my R7800, I don't know what happened but the update was done and the router rebooted correctly but I wasn't able to enter in the router via ssh, ping it or access to the GUI. After a router reset all was ok but after I changed some settings the router hanged again! I think I was changing the QoS setting (the router was up and running from the LEDs but I cannot access to it). Reset again, then I switched back to the old r34115M (done a NVRAM reset) and all is fine...
Anyway I still have both the core with independent speed showed in the info pages
EA8500
34175M K4.9.71
working very well for me
I guess the 'unknown event ID' has been squashed thanks for that
Been using DNSCrypt + DNSSEC w/ dnscrypt.ca Server 2 ... these guys are dang good and also will pass just
about every DNSSEC resolver algorithm test ---- even better than unbound
And their server certs are updated every 24hr with new superseding old without a bleep.
DNSMasq cache-size=5120 all good.... so imma leave well enough alone but it will be put thru the test
next couple days ---- prolly won't see my WAN off max DL rate for a while.
:~# dmesg | tail
[ 40.013917] br1: port 2(ath1.1) entered forwarding state
[ 40.013941] br1: topology change detected, propagating
[ 41.374323] br1: port 3(vlan4) entered learning state
[ 43.453940] br1: port 3(vlan4) entered forwarding state
[ 43.453961] br1: topology change detected, propagating
[ 50.010242] Ebtables v2.0 registered
[24765.285980] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[24765.286033] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[24765.293176] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[24765.301393] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
:~# uptime
07:17:26 up 1 day, 22:13, load average: 0.13, 0.07, 0.01
:~# date
Sun Dec 24 07:17:29 CST 2017
--- and as a side note for EA8500 users ---
r34191 std (12/23/17) Linux 4.14.9-rc1
is working but still needs a manual switch reboot after changing many settings cause of lockup.
No EA8500 build yet with very latest BS fixes but I reckon when he compiles one it'll be much better
So there is hope with new bleeding-edge kernel stuff ....... heck my debian rig is only running 4.13.0-1-amd64
I'm seeing an interesting issue with the last few builds I've tested - the options in some config pages repeat 2x.
Going back several months in builds this issue doesn't exist.
I've cleared NVRAM several times, but when I apply settings on some pages it will start this issue. Does not disappear on reboot, only way to get it to stop is clear everything out, so it seems to be something that's being stored by the pages in NVRAM like a bad variable that starts this strange behavior.
Joined: 16 Nov 2015 Posts: 7391 Location: UK, London, just across the river..
Posted: Mon Dec 25, 2017 7:59 Post subject:
chrisf8657 wrote:
I'm seeing an interesting issue with the last few builds I've tested - the options in some config pages repeat 2x.
Going back several months in builds this issue doesn't exist.
I've cleared NVRAM several times, but when I apply settings on some pages it will start this issue. Does not disappear on reboot, only way to get it to stop is clear everything out, so it seems to be something that's being stored by the pages in NVRAM like a bad variable that starts this strange behavior.
Tried this build on R7800 with settings reset. It did not do any strange behavior, hangs or other errors with basic features usage. More, this 4.14 kernel with exact same settings, same device in the same spot is getting better signal than with the 4.9 kernel build.
Thanks to the devs! Some very merry holidays and a good 2018 ahead!
and no more uglies in the log.