So I've been using build 35530 a few days now. Just got the router on Monday. I've been very impressed. Looking forward to getting some opkg stuff added and trying that out. I have an old external hard drive I'm going to try to attach and get it set up as a torrenting drive and media server for my network. I saw kong builds used to have transmission built in. I guess it doesn't any more correct? I'll have to add it myself?
or bs builds from the list below in red font. if ur going to use bs builds there is 2 extra commands that need to be run since kernel 4.x is broken shit.
mind showing or listing the nic settings used for the intel wifi? ac 8500 doesnt exist so maybe 8260.? _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
or bs builds from the list below in red font. if ur going to use bs builds there is 2 extra commands that need to be run since kernel 4.x is broken shit.
mind showing or listing the nic settings used for the intel wifi? ac 8500 doesnt exist so maybe 8260.?
What extra commands? The governors and irq balancing? _________________ R6400v2 (boardID:30) - Kong 36480 running since 03/09/18 - (AP - DNSMasq - AdBlocking - QoS) R7800 - BS 31924 running since 05/26/17 - (AP - OpenVPN Client - DNSMasq - AdBlocking - QoS) R7000 - BS 30771 running since 12/16/16 - (AP - NAS - FTP - SMB - OpenVPN Server - Transmission - DDNS - DNSMasq - AdBlocking - QoS) R6250 - BS 29193 running since 03/20/16 - (AP - NAS - FTP - SMB - DNSMasq - AdBlocking)
or bs builds from the list below in red font. if ur going to use bs builds there is 2 extra commands that need to be run since kernel 4.x is broken shit.
mind showing or listing the nic settings used for the intel wifi? ac 8500 doesnt exist so maybe 8260.?
What extra commands? The governors and irq balancing?
or bs builds from the list below in red font. if ur going to use bs builds there is 2 extra commands that need to be run since kernel 4.x is broken shit.
mind showing or listing the nic settings used for the intel wifi? ac 8500 doesnt exist so maybe 8260.?
Huh, somehow I misread it Yes, the 8260 is correct..Where do I get the NIC?
or bs builds from the list below in red font. if ur going to use bs builds there is 2 extra commands that need to be run since kernel 4.x is broken shit.
mind showing or listing the nic settings used for the intel wifi? ac 8500 doesnt exist so maybe 8260.?
Huh, somehow I misread it Yes, the 8260 is correct..Where do I get the NIC?
for windows, network connections, right click the adapter, properties, configure, advanced tab, there will be a bunch of settings. looks like the image. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
idk the last time i saw anything on our svn with that or qos period..
I don't use DD-WRT but I feel I had to respond to this.
DD-WRT has a version of ath10k with a lot of local changes whereas OpenWrt's is mostly stock. Furthermore I'm fairly certain BrainSlayer has the source to the firmware under NDA. You're asking why you don't get firmware from some other guy with the source.
As for the cake stuff, I believe that requires a newer kernel than what's in DD-WRT (3.16?). I could be wrong.
Btw is WiFi stable in DD-WRT? ath10k in OpenWrt (both driver and firmware) is a complete joke. QCA has some real quality control problems...
idk the last time i saw anything on our svn with that or qos period..
I don't use DD-WRT but I feel I had to respond to this.
DD-WRT has a version of ath10k with a lot of local changes whereas OpenWrt's is mostly stock. Furthermore I'm fairly certain BrainSlayer has the source to the firmware under NDA. You're asking why you don't get firmware from some other guy with the source.
As for the cake stuff, I believe that requires a newer kernel than what's in DD-WRT (3.16?). I could be wrong.
Btw is WiFi stable in DD-WRT? ath10k in OpenWrt (both driver and firmware) is a complete joke. QCA has some real quality control problems...
i dont know what our driver has as most commits for it is done under "auto commit of driver changelogs" with the most bland commit messages possible, the firmwares are stock, he tried the ct firmware once years ago then gave up on it a day later cause he said it was crashing in client mode, while mine was working fine. brainslayer said both about firmware, having the source, then being annoyed at qca for not giving the source and back and forth between them *shrug*. he also claimed to me that if he had the source, he'd go and fix everything up. im not seeing many fixes.
intel ac 7260 the qca9980/9984 cannot handle in ac mode whatsoever, even modest tx traffic to a ac 7260 client will cause the radio noise level go from like -105 to -60, entire radio hangs for several seconds, clients drop etc. only happens on 5ghz ac mode, on 5ghz n mode or 2.4ghz radio, no issue. ONLY qca9980/9984 + ddwrt does that, the same radios on stock fw, fine. other radios on ddwrt, fine. but typically with BS, its clients' fault, or "works for me so no issue". i gave up after years and have a bcm4352 mpcie card coming, will see how it treats that..
r7800 has only been on k3.18 since supported, few months ago it was moved to k4.9/4.14 which absolutely destroyed qos. more than doubled the latency on download at "high speeds", 65mbps+, hfsc is absolutely unusable now at such speeds as well. cpu freq is broken, the clock scales fine but when enabled cpu load on absolutely everything is high, so high u cant even reach throughput max of a 2x2:2 ac 80mhz device before the cpu saturates from interrupts. this also affects qos performance even more on top of the doubled latency issue. cpu freq scaling problem is (MOSTLY) worked around by setting performance governor or manually setting min freq to 1725000 for both cores. when i last tried lede a couple months ago it was 17.01.4, the same cpu load issue was present from the freq scaling problem in k4.x but at that time it wasnt known that it was cpu freq scaling causing it.
along with k4.x switch PIE was removed for no reason, its among the best that we currently have for high speeds once coupled with a few port priorities. the ticket for that is http://svn.dd-wrt.com/ticket/6115 if u want to look at it. the only fix thats happened since then was the jittery upload since tc wasnt working..but thats it. download latency is still complete shit. but as usual especially with qos, BS doesnt care, he never has. if u dig back long enough ull find us begging for addition of fq_codel, finally came after years and being told no. now we're at it again with cake (and readdition of PIE).. might be decades this time.
thats in BS builds, kong actually listened to us and fairly quickly reverted to k3.18 on his builds, so qos is better there by a lot (not counting old qos issues that affect all routers and been here longer than i have), has PIE, and theres no issue with load from cpu freq scaling.
wifi is acceptable (not counting how it cant handle intel ac 7260) for the most part, once setup correctly, it's biggest issue is we have a truck load of invalid settings that can be easily picked with channels, such as 80mhz 149+UL when its UU only, 161 displaying all other options when its LL only, etc. in 80mhz mode our last channel is 165, where kong has it right on his builds, when it should be 161. ticket for that is http://svn.dd-wrt.com/ticket/5699 but.. BS is right all issues reported are "bullshit" (literally, hes said that to me more than twice).. doesnt even listen to his partner dev kong either.
That's...kind of surprising. I'd think DD-WRT would have some proprietary magic.
I know DD-WRT has local patches for the driver. Guess not the firmware...weird.
He should try the CT firmware again. Ben has fixed a ton of bugs. It's pretty stable at least on OpenWrt. I've switched to that on my local builds since stock driver and firmware are trash.
Joined: 21 Jul 2006 Posts: 1898 Location: Fortaleza Ce Brazil
Posted: Thu Mar 29, 2018 22:26 Post subject:
Hi guys ..
Since last 3 mounths , Kongs builds and my settings in my R7800 is stable .. Last february it works flawless for 30 days .. My settings are not basic .. i think Kong last test builds leave most satisfied . If i could give a grade it will get 95 .
yes .. there are something to improve and finished , but devs are doing a fantastic job ..
Thats it
_________________ DDwrt ...it rocks ....
1 R7800 54420 AP Wireguard webserver JFFS SAMBA FTP usb HD Mesh
1 R7800 54420 Cli Mesh
1 WZR1750 54389 AP Webserver Samba Wireguard
1 TP link Archer C7v5 54420 Cli Mesh
1 DD x86_64 48296 Gateway Samba Ftp Webserver
There is no perfect hardware and software in the world but r7800 with ddwrt Kong build is best router i ever had. Its amazingly stable and fast _________________ Netgear R7800
I'd like to say that R7000/R7800 with DD-WRT is the best I've ever used too because it did so much right, but it's actually complete unusable because of the huge lag spikes like the OpenWrt link above. I'm not sure if BS/Kong have resolved this haven't been back in a couple months to test but haven't heard of any fixes.
Because of this issue I'm forced to use the OEM firmware which works perfect and has no lag spikes but has the worst UI I've ever seen.
interesting.. but im having a hard time understanding it.. are they referring to the latency increase of k4.x with qos or this some other new(or old) latency issue..? _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Yes, the 8260 is correct..Where do I get the NIC?