looking at timeline this just looks like a marvell release, qualcomm support has fallen apart recently. only difference i can see is the random wrong macs are fixed, ath9k performance is slightly better & thats it..nothing else fixed like dupe macs, tx rate, qos, wifi drops on key renewal, missing vht80+80 on qca9984 etc... _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Router: TL-WDR3600
Status: Bad
Reset: Reset to defaults after flashing, then erased NVRAM
Errors: See below
Wireless keeps dropping out on my Android phone, and that was when it was on the 2.4 GHz band. It only took walking about 10 feet from the AP and the wireless signal diminished rapidly. That is because of this build, not my phone or signal propagation. When the phone was connected on the 5 GHz band, the wireless performance was even worse. I have the AP set to "N Only" for the 5 GHz band and am not sure if you are supposed to leave it on "Mixed" these days, as the wiki stated or if "N Only" is working now.
Modello Router TP-Link TL-WR841ND v9
Versione Firmware DD-WRT v3.0-r30796 std (10/25/16)
Versione Kernel Linux 3.18.42 #2134 Tue Oct 25 05:00:29 CEST 2016 mips
Status: OK
Reset: No
Errors: WiFi don't work (i have try).
looking at timeline this just looks like a marvell release, qualcomm support has fallen apart recently. only difference i can see is the random wrong macs are fixed, ath9k performance is slightly better & thats it..nothing else fixed like dupe macs, tx rate, qos, wifi drops on key renewal, missing vht80+80 on qca9984 etc...
tx rate. qca -> blame qca. firmware does not show tx rates
80+80 support. known issue->blame qca. firmware is buggy in 80+80. use vht160 which works. dupe macs? no issue. macs are used as preconfigured. multiple interfaces may have the same mac. this isnt a issue and this is wanted by some vendors. consider. i use a r7800 every 2 (2 in fact). no issues with rekeying. since qca has not released any firmware updates yet, you have to wait _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
Joined: 24 Feb 2013 Posts: 1634 Location: Belgrade
Posted: Wed Oct 26, 2016 19:17 Post subject:
Router Model TPLINK WR1043ND V2
Firmware Version DD-WRT v3.0-r30796 std (10/25/16)
Kernel VersionLinux 3.18.42 #2140 Tue Oct 25 05:05:41 CEST 2016 mips
Router Model TP-Link TL-WR740N v4
Firmware Version DD-WRT v3.0-r30796 std (10/25/16)
Kernel Version Linux 3.10.104 #3410 Tue Oct 25 04:32:10 CEST 2016 mips
Router Model GL.iNet-AR150
Firmware Version DD-WRT v3.0-r30796 std (10/25/16)
Kernel Version Linux 3.18.42 #2172 Tue Oct 25 06:13:47 CEST 2016 mips
Reset: No
Status: Working
Errors: None so far (didn't tested hotspot yet). Wifi is rock solid on my units, dnsmasq and ipv6 works... will test nDPI newer code to see if there is any difference...
Joined: 24 Feb 2013 Posts: 1634 Location: Belgrade
Posted: Wed Oct 26, 2016 19:21 Post subject:
for last 10 builds (aprox.) my CPU load is very high after every reboot (2,5)... I increased Maximum Ports from 4096 to 8192 (management tab) and I noticed that unit is much more stable... GUI is faster... maybe it is not relevant but I just noticed...
looking at timeline this just looks like a marvell release, qualcomm support has fallen apart recently. only difference i can see is the random wrong macs are fixed, ath9k performance is slightly better & thats it..nothing else fixed like dupe macs, tx rate, qos, wifi drops on key renewal, missing vht80+80 on qca9984 etc...
tx rate. qca -> blame qca. firmware does not show tx rates
80+80 support. known issue->blame qca. firmware is buggy in 80+80. use vht160 which works. dupe macs? no issue. macs are used as preconfigured. multiple interfaces may have the same mac. this isnt a issue and this is wanted by some vendors. consider. i use a r7800 every 2 (2 in fact). no issues with rekeying. since qca has not released any firmware updates yet, you have to wait
the dupe macs on dir-862L are not preconfigured, stock fw has different macs & the problems of dupe macs dont occur there.
there is no rekeying issue with r7800 except for wds. the wds ap must be ath10k, the wds sta must also be ath10k, setting the wds ap key renewal to 0 is a workaround. this happens on qca98xx too same thing if its the wds ap.
the rekeying problem is with ath9k or mac80211 but only affecting ath9k radios, lots of drops when power save devices are idle or using light traffic <100kbps, cant even get 10 min uptime. revert fw problem is gone, OR set key renew int to 0 problem is gone. it doesnt drop them on every rekey, but 80% of them. thats why in the ticket i say to set key renewal int to 30 second to make testing faster, within a couple mins power save devices will all drop. non power save device are fine. there was lots of mac80211 changes recently, ccmp, fq, etc, something broke.
EA8500
DD-WRT v3.0-r30796 std (10/25/16)
Linux 3.18.42 #108 SMP PREEMPT Fri Oct 14 01:03:03 CEST 2016 armv7l
install live over 30731M
NO Good here -
Seemed to work while its running but I couldn't get it to stay up over few min
Reboots itself...
It also changed permissions to READ ONLY on the SAMBA Share FAT32 flash
drive mounted /tmp/mnt/sda1 although didn't show being changed in any obvious place.
Yea that's weird. Booted back into 30731M and still only had READ ONLY.
Hit Apply Settings in Services/NAS and all back to normal...No file corruption.
I did compare smb.conf from both builds and not a thing different there.
Oh well -- 30731M is a good build on the ea8500.
This at end of dmesg is a new one -
[ 31.901530] xt_ndpi 3.0 (nDPI wrapper module).
all other errors / warnings / notices are 'bout same as 30731M
'EA8500_30796-dmesg.txt'
From kernel date --- don't look like anyone has tinkered with this build much in a while --
If get good backup router in order I might do an erase nvram and have better look-see.
So i was talking to kong a while ago and this was the first message i sent him
Quote:
Router Name: R7500v2CB
Router Model: Netgear R7500v2
Firmware Version: DD-WRT v3.0-r30796 std (10/25/16)
Kernel Version: Linux 3.18.42 #108 SMP PREEMPT Fri Oct 14 01:03:03 CEST 2016 armv7l
Status: working
Reset: no factory reset
Errors:
It appears that, and after doing some googling on this function, "Web Services on Devices" or WSP is unable to work properly on the client bridge setup when it comes to this router along with other non-broadcom units
So basically any computers that are connected to the "R7500v2CB" will be unable to see the wireless printer connected to the Main AP but can at least see other computers.
The reason why i am back up again with this is that although i got wireless printing working, i am unable to use the scanner across the network like i was in the past.
And from he told me, the drivers still need some work. So i will wait. But as far as everything else, Its working well in client bridged mode. I do have it set to schedule a reboot every day at 3am.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Thu Oct 27, 2016 2:29 Post subject:
Gameman Advanced Kid wrote:
So i was talking to kong a while ago and this was the first message i sent him
Quote:
Router Name: R7500v2CB
Router Model: Netgear R7500v2
Firmware Version: DD-WRT v3.0-r30796 std (10/25/16)
Kernel Version: Linux 3.18.42 #108 SMP PREEMPT Fri Oct 14 01:03:03 CEST 2016 armv7l
Status: working
Reset: no factory reset
Errors:
It appears that, and after doing some googling on this function, "Web Services on Devices" or WSP is unable to work properly on the client bridge setup when it comes to this router along with other non-broadcom units
So basically any computers that are connected to the "R7500v2CB" will be unable to see the wireless printer connected to the Main AP but can at least see other computers.
The reason why i am back up again with this is that although i got wireless printing working, i am unable to use the scanner across the network like i was in the past.
And from he told me, the drivers still need some work. So i will wait. But as far as everything else, Its working well in client bridged mode. I do have it set to schedule a reboot every day at 3am.
well client bridge is hacky in nature..its basically combining the bridge like wds with the compatibility like client (non bridge) mode. brainslayer told me all about it & there will pretty much be no fix, it might sway left or right a bit as driver versions change but thats how it is.. if anything, blame IEEE for not making a WDS spec. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
I've just been given a TPLINK_TL-WR2543ND, on the FTP I can only see TPLINK_TL-WR2543, is that the same router even without the ND on the end? _________________ TPLINK TL-WR2543ND (5GHz)
WRT160NL (2.4GHz)
