Linksys EA8500
DD-WRT v3.0-r34311 std (12/29/17)
Linux 4.9.72 #31 SMP PREEMPT Thu Dec 28 03:42:28 CET 2017 armv7l
Tis worky ok. ... AFAICT is the same EA8500 build some of us have been playing with here -
https://www.dd-wrt.com/phpBB2/viewtopic.php?p=1110276#1110276
So it's ok. I installed on main router cause if I didn't it'll cause my OCD to itch.
You with the high speed 100+ connections should read those last couple pages if not already
following the EA8500 thread. Any related info might help fix high speed QOS.
Top Light still don't work -
cheers -
actually this is last dmesg pulled from r34299
Don't let this scare you -- AFAIK tis harmless, only an infernal part of using new firmware
[ 47.904095] Ebtables v2.0 registered
[40642.642503] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[40642.642542] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[40642.649735] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[40642.657824] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[40642.665995] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[40642.674150] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[40642.682301] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[40642.690526] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[40975.814736] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[41744.446065] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44071.210999] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44071.211045] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44071.218278] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44071.226441] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44071.234577] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44071.242646] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44071.250884] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44071.259038] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44071.267208] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44071.275377] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44236.325094] ath10k_warn: 6 callbacks suppressed
[44236.325110] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44236.328467] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44236.336889] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44236.345042] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44236.353115] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44236.361400] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44236.369533] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44236.377718] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44236.385841] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44236.393993] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44257.331349] ath10k_warn: 41 callbacks suppressed
[44257.331356] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44257.335102] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44257.343108] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[44257.351335] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[48117.950651] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[48117.950683] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[48117.957913] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[48117.966045] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[48117.974197] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[48117.982286] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[48117.990513] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[49549.866193] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[49549.866284] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[49549.873348] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[49549.881600] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[49549.889746] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[49549.897897] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[49549.906064] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[49549.914204] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[49549.922308] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[49549.930543] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[50642.766754] ath10k_warn: 38 callbacks suppressed
[50642.766772] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[50642.770498] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[50642.778689] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[50642.786790] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[50642.794944] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[50642.803044] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[50642.811252] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[50642.819437] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[50642.827560] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[50642.835744] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[55123.406038] ath10k_warn: 10 callbacks suppressed
[55123.406051] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[55123.409839] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[57734.639560] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[57734.674925] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[57734.676738] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[57734.712276] ath10k_pci 0001:01:00.0: Unknown eventid: 36925
[59920.482418] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[59920.482450] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[64117.180346] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[64117.198300] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[64118.258305] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[64118.275615] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
root@~:~# uptime
07:33:33 up 1 day, 4 min, load average: 0.08, 0.04, 0.03
done being a broken record, qos info is in tickets 6113, 6115, 6127.. maybe now that its pretty much ruined itll get some attention in 2018.. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Posted: Fri Dec 29, 2017 17:34 Post subject: Upgrade
Router/Version: TP-Link Archer C7 v2
Firmware: 34311
Previous: 34080
Mode/Status: WDS AP, WDS Station
Reset: No
Issues/Errors: None, so far.
Router/Version: TP-Link WDR3600 v1
Firmware: 34311
Previous: 34080
Mode/Status: WDS Station
Reset: No
Issues/Errors: None, so far.
Router/Version: TP-Link TL-WR841ND v8
Firmware: 34311
Previous: 34080
Mode/Status: WDS Station
Reset: No
Issues/Errors: None, so far.
Router/Version: D-Link DIR-825 B1
Firmware: 34311
Previous: 34080
Mode/Status: WDS Station
Reset: No
Issues/Errors: None, so far.
Router/Version: D-Link DIR-862L A1
Firmware: 34311
Previous: 34080
Mode/Status: WDS Station
Reset: Yes.
Issues/Errors: None, so far. _________________ Before asking a question on the forums, update dd-wrt: Where do I download firmware? I suggest reading it all.
QCA Best WiFi Settings
Some dd-wrt wiki pages are up to date, others are not. PM me if you find an old one.
Atheros:
Netgear R7800 x3 - WDS AP / station, gateway, QoS
TP-Link Archer C7 v2 x2 - WDS Station
TP-Link TL-WDR3600 v1 - WDS Station
TP-Link 841nd v8 - NU
D-Link 615 C1/E3/I1 x 7 - 1 WDS station
D-Link 825 B1 - NU
D-Link 862L A1 x2 - WDS Station
Netgear WNDR3700v2 - NU
UBNT loco M2 x2 - airOS
Broadcom
Linksys EA6400 - Gateway, QoS
Asus N66U - AP
Netgear WNDR3700v3 - not used
MediaTek
UBNT EdgeRouter X - switch
Router/Version: Netgear WNDR3700 v2
Firmware: 34311
Previous: 34080
Kernel Version: Linux 3.10.108 #46016 Fri Dec 29 03:57:44 CET 2017 mips
Mode/Status: AP and Virtual AP
Reset: No
Issues/Errors: Resets on heavy use, clients loose connection for about 15 seconds - doing a speedtest.net test for example would cause a reset. Reverted back to r34080.
Last edited by ciscodlink on Fri Dec 29, 2017 23:03; edited 4 times in total
Joined: 30 Jan 2015 Posts: 676 Location: Texas, USA
Posted: Fri Dec 29, 2017 21:03 Post subject:
NiTrus wrote:
NETGEAR R9000
DD-WRT v3.0-r34311 std (12/29/17)
Linux 4.9.72 #31 SMP PREEMPT Thu Dec 28 03:42:28 CET 2017 armv7l
ath0/5ghz came up on upgrade, crashed, rebooted multiple times..would not come back up..went back to Kongs working build..
Hmmm, I didn't see any issues in updating and so far working fine. I have two R9000s AP and repeater bridge. _________________ 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
Joined: 25 Dec 2010 Posts: 295 Location: Twin Cities, MN
Posted: Fri Dec 29, 2017 23:15 Post subject:
jerrytouille wrote:
NiTrus wrote:
NETGEAR R9000
DD-WRT v3.0-r34311 std (12/29/17)
Linux 4.9.72 #31 SMP PREEMPT Thu Dec 28 03:42:28 CET 2017 armv7l
ath0/5ghz came up on upgrade, crashed, rebooted multiple times..would not come back up..went back to Kongs working build..
Did you erase nvram as switching from Kong to BS build?
just tryed erase nvram, worked...ive never had to before, going between their firmwares..
must have needed to... _________________ NETGEAR R9000 | RT | 40134 NETGEAR R7800 | AP | 40134
Posted: Sat Dec 30, 2017 1:34 Post subject: EA8500 clients don't connect to the router anymore
I upgraded my wrt3200zc and archer C9 V1 no problem so far
But when I upgraded my EA8500 no client could get an ip anymore.
I downgraded and it worked ok than upgraded again and the same problem no client could connect nor could I see any leases in the interface
I'm back to the old R34080 on the linksys EA8500 for now
