Broadcom K3.X testing, test users wanted

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3 ... , 54, 55, 56  Next
Author Message
shadowlmd
DD-WRT Novice


Joined: 27 Sep 2017
Posts: 5

PostPosted: Mon Oct 16, 2017 21:21    Post subject: Reply with quote
jwh7 wrote:
N66U is reported working with 33492:
http://www.dd-wrt.com/phpBB2/viewtopic.php?p=1098661#1098661

Great news! I flashed my device and it didn't get bricked. Smile I wonder if `mega` would be safe to flash, though, I used that one before. Anyway, thank you very much for this update!
Sponsor
Whammy
DD-WRT User


Joined: 14 Aug 2007
Posts: 50

PostPosted: Tue Oct 17, 2017 0:36    Post subject: Reply with quote
10/10/2017 3.x build does not flash on the WNR3500L. File is still too big.

Needs to be 7.3MB like the 7/27/2017 build.
mikeazo
DD-WRT Novice


Joined: 18 Oct 2017
Posts: 2

PostPosted: Wed Oct 18, 2017 13:02    Post subject: Reply with quote
I will do some more testing when I can, but when I installed r33525 on my Asus RT-N16 last night (mega), everything went fine for the install. However, when I enabled clone mac address and rebooted, I lost my connection, wireless and wired. Setting a static IP did not help either.

Anyone else experience this?
alazred
DD-WRT Novice


Joined: 10 Mar 2013
Posts: 1

PostPosted: Fri Oct 20, 2017 7:00    Post subject: RT-N16 r33525 Reply with quote
Hi, I'm searching that revision for my rt-n16 and can't find it. Where did you got it from?

Thx
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 1765
Location: Indy

PostPosted: Tue Oct 24, 2017 15:35    Post subject: Re: RT-N16 r33525 Reply with quote
alazred wrote:
Hi, I'm searching that revision for my rt-n16 and can't find it. Where did you got it from?
In the broadcom_K3X folder:
ftp://ftp.dd-wrt.com/betas/2017/10-17-2017-r33525/broadcom_K3X/dd-wrt.v24-33525_NEWD-2_K3.x_mega_RT-N16.trx
But you might as well use the 33555 build now, or wait for the next one w/ the Broadcom KRACK fix.

_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: Builds, Types, Modes, Changelog, Peacock, Demo #
x64 OPNsense 18.7b65|EA6900v1.1 Xwrt 380.70|DD: 35927 WNDR4500v2, WNDR4000@533, E1500@353, R6300v1,
2*E2500, WRT54*@250: GLv1.1 nks, GSv6 µ
|RT-N66U@663 Merlin 380.70|OEM: WGR614v10@400-WNR1000v3 mod
Madmanguruman
DD-WRT User


Joined: 06 Nov 2010
Posts: 50
Location: Canada

PostPosted: Thu Nov 02, 2017 0:37    Post subject: Reply with quote
dd-wrt.v24-33607_NEWD-2_K3.x_mega_RT-N12.trx seems to be working well on my RT-N12 D1. Serial CFE/TFTP'd the file direct from stock, LAN and wireless seem to be working (currently configured as a client bridge).
Whammy
DD-WRT User


Joined: 14 Aug 2007
Posts: 50

PostPosted: Mon Nov 06, 2017 0:18    Post subject: Reply with quote
There are no K3 11/04 builds.
mikaël
DD-WRT Novice


Joined: 02 Sep 2008
Posts: 3

PostPosted: Tue Nov 07, 2017 6:51    Post subject: Reply with quote
Hi, I am using V3.0-r29218 mega (03-07-16) on e4200.
It works fine.

Now I need it, I am surprised that Rflow is gone.
Is rflow back on newer version ?
If not, is it on newer 2.6 ?

Thanks,
thracx
DD-WRT Novice


Joined: 14 Apr 2010
Posts: 18

PostPosted: Thu Nov 09, 2017 5:51    Post subject: Asus RT-N16 with DD-WRT K3 r33607 Big Reply with quote
The latest K3 version* appears to be working on my Asus RT-N16 without issue, although it did require a reasonably complicated flashing process to get it working.

I am not a heavy WiFi user, but initial tests are showing 330Mpbs speeds over WAN.


* The actual latest release (11-04-2017-r33679) did not provide a K3 option, so the build used was r33607_NEWD-2_K3.x-big.

_________________
-Thracx

"Man wants to know, and when he ceases to do so, he is no longer a man."
-Fridtjof Nansen
Kali_B_Linux
DD-WRT Novice


Joined: 11 Oct 2017
Posts: 4
Location: New York, USA

PostPosted: Sat Nov 25, 2017 17:25    Post subject: Reply with quote
I will start posting results from my e1200v2 router. I have been busy but expect to be more active in the community over the next few weeks.
native_tx
DD-WRT User


Joined: 26 Feb 2014
Posts: 122
Location: Texas

PostPosted: Tue Nov 28, 2017 12:05    Post subject: Reply with quote
I had tried the r33607 & r33772 mega builds for my E3200 and both loaded fine with no issues, no performance issues to the 2.4ghz but the only problem that always stands out is the Qos just enabling it takes 65% of the ingress bandwidth, the egress performance had no issues. I sat around most of the day troubleshooting on those two builds, reading from dd-wrt wiki on qos to see if there was something adding that I had already knew of but not much has changed, I used on different settings on either the netmask set to single ip or mac and used either the premium or express both performed ok, let say that I have a 100/10 connection after running several test i did a average and was 119/11. Placing around 80% of the ingress value in and ran ping test while speed testing the ingress was always at 57mbps/8mbps no matter what value I placed for the ingress it didn't move from 57, but once i did 10% of the 57Mbps then the ingress pings were lowering to a the 20ms no packet loss, ok now I decided to unplug and wait after each setting and ran the test all over again with same conclusion that showed a proper response from the same values that I placed to those results I did earlier
. Now I decided to do the same test again unplug and power up on different the codel and htb same results and with same conclusion until i did the same as before to receive a positive response and lower ms ping and same with hsfc and fq_codel same until I reproduced the again settings to lower the ms ping. The same with the previous build r33607 as the same method I did with r33772. I checked and noticed if I had issues with sirq and that worked up abit and could have made that happen during those tests but still I took a look at the traffic control of the same settings with fq_codel/codel with htb or hsfc and checked after powering down and then up, flashing or clearing nvram there seems to be a problem with an unknown qdisc involved that not loading.

# tc -s qdisc ls dev imq0
qdisc htb 1: root refcnt 2 r2q 10 default 30 direct_packets_stat 0
Sent 10275392 bytes 8608 pkt (dropped 0, overlimits 8079 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 100: parent 1:100 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 10: parent 1:10 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 20: parent 1:20 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 30: parent 1:30 [Unknown qdisc, optlen=48]
Sent 224140 bytes 542 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 40: parent 1:40 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 211: parent 1:211 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 212: parent 1:212 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 213: parent 1:213 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 214: parent 1:214 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 215: parent 1:215 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 221: parent 1:221 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 222: parent 1:222 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 223: parent 1:223 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 224: parent 1:224 [Unknown qdisc, optlen=48]
Sent 10051252 bytes 8066 pkt (dropped 366, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 225: parent 1:225 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 231: parent 1:231 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 232: parent 1:232 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 233: parent 1:233 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 234: parent 1:234 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 235: parent 1:235 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
---------------------------------

root@dd-wrt:~# tc -s qdisc ls dev eth0
qdisc pfifo_fast 0: root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
Sent 2261708145 bytes 3827251 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
--------------------------------

root@dd-wrt:~# tc -s qdisc ls dev eth1
qdisc pfifo_fast 0: root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
Sent 4076809671 bytes 2935658 pkt (dropped 0, overlimits 0 requeues 3)
backlog 0b 0p requeues 3
--------------------------------

root@dd-wrt:~# tc -s qdisc show
qdisc pfifo_fast 0: dev eth0 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
Sent 2261778319 bytes 3827644 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc pfifo_fast 0: dev eth1 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
Sent 4076829713 bytes 2935700 pkt (dropped 0, overlimits 0 requeues 3)
backlog 0b 0p requeues 3
qdisc htb 1: dev vlan2 root refcnt 2 r2q 10 default 30 direct_packets_stat 0
Sent 2521566 bytes 8595 pkt (dropped 476, overlimits 872 requeues 0)
backlog 0b 0p requeues 0
qdisc htb 1: dev imq0 root refcnt 2 r2q 10 default 30 direct_packets_stat 0
Sent 10509573 bytes 9015 pkt (dropped 0, overlimits 8079 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 100: dev imq0 parent 1:100 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 10: dev imq0 parent 1:10 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 20: dev imq0 parent 1:20 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 30: dev imq0 parent 1:30 [Unknown qdisc, optlen=48]
Sent 444229 bytes 884 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 40: dev imq0 parent 1:40 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 211: dev imq0 parent 1:211 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 212: dev imq0 parent 1:212 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 213: dev imq0 parent 1:213 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 214: dev imq0 parent 1:214 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 215: dev imq0 parent 1:215 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 221: dev imq0 parent 1:221 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 222: dev imq0 parent 1:222 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 223: dev imq0 parent 1:223 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 224: dev imq0 parent 1:224 [Unknown qdisc, optlen=48]
Sent 10065344 bytes 8131 pkt (dropped 366, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 225: dev imq0 parent 1:225 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 231: dev imq0 parent 1:231 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 232: dev imq0 parent 1:232 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 233: dev imq0 parent 1:233 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 234: dev imq0 parent 1:234 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 235: dev imq0 parent 1:235 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc pfifo_fast 0: dev imq1 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0

I didn't copy the output of when I used just htb/sfq or hsfc/sfq but I did notice that they loaded properly but the problem still that my ingress wasn't properly being handle as I thought to be as it just hung around to 57mbps these test I performed were on a gigabyte laptop connected directly to the router, the router performed perfectly and is able to achieve the said bandwidth from the ISP as they give those extra download/upload bandwidth. I also did these tests on the stock and if performed well just the qos doesn't control download but It still performed as it should have to what the ISP is sending to their transparent emta telephony. I kinda looking for someone else to look into and post an output of their traffic output of a build in the broadcom k3x mega build if you or were having the same type of problem with qos. I'm going to do the same test on the k2.6 build today and post some of those results since they do no obviously don't have the codel/fq_codel built into them and knowing that shouldn't have any influence on the performance of qos in slightest. This is just something that has kinda been puzzling even though you may say it's a under powered soho and could say yes to that only that I'm not on a network that is demanding on anything other than just web browsing, some xbox/ps gaming, no torrents, no proxy, no vpn, nothing to kill a small routers performance just to enable Qos, and I had installed lede/openwrt before and used some those sqm scripts fq_codel/ simple.qos or cake/piece of cake with a positive results of course they don't have wifi but it was all for testing performance anyways. Thank you for reading this long post and I apologize if I placed this post into here as I was wanting to make aware of this issue and some results of type of testing with the hours that it took.
native_tx
DD-WRT User


Joined: 26 Feb 2014
Posts: 122
Location: Texas

PostPosted: Tue Nov 28, 2017 21:08    Post subject: Reply with quote
native_tx wrote:
I had tried the r33607 & r33772 mega builds for my E3200 and both loaded fine with no issues, no performance issues to the 2.4ghz but the only problem that always stands out is the Qos just enabling it takes 65% of the ingress bandwidth, the egress performance had no issues. I sat around most of the day troubleshooting on those two builds, reading from dd-wrt wiki on qos to see if there was something adding that I had already knew of but not much has changed, I used on different settings on either the netmask set to single ip or mac and used either the premium or express both performed ok, let say that I have a 100/10 connection after running several test i did a average and was 119/11. Placing around 80% of the ingress value in and ran ping test while speed testing the ingress was always at 57mbps/8mbps no matter what value I placed for the ingress it didn't move from 57, but once i did 10% of the 57Mbps then the ingress pings were lowering to a the 20ms no packet loss, ok now I decided to unplug and wait after each setting and ran the test all over again with same conclusion that showed a proper response from the same values that I placed to those results I did earlier
. Now I decided to do the same test again unplug and power up on different the codel and htb same results and with same conclusion until i did the same as before to receive a positive response and lower ms ping and same with hsfc and fq_codel same until I reproduced the again settings to lower the ms ping. The same with the previous build r33607 as the same method I did with r33772. I checked and noticed if I had issues with sirq and that worked up abit and could have made that happen during those tests but still I took a look at the traffic control of the same settings with fq_codel/codel with htb or hsfc and checked after powering down and then up, flashing or clearing nvram there seems to be a problem with an unknown qdisc involved that not loading.

# tc -s qdisc ls dev imq0
qdisc htb 1: root refcnt 2 r2q 10 default 30 direct_packets_stat 0
Sent 10275392 bytes 8608 pkt (dropped 0, overlimits 8079 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 100: parent 1:100 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 10: parent 1:10 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 20: parent 1:20 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 30: parent 1:30 [Unknown qdisc, optlen=48]
Sent 224140 bytes 542 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 40: parent 1:40 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 211: parent 1:211 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 212: parent 1:212 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 213: parent 1:213 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 214: parent 1:214 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 215: parent 1:215 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 221: parent 1:221 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 222: parent 1:222 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 223: parent 1:223 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 224: parent 1:224 [Unknown qdisc, optlen=48]
Sent 10051252 bytes 8066 pkt (dropped 366, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 225: parent 1:225 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 231: parent 1:231 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 232: parent 1:232 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 233: parent 1:233 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 234: parent 1:234 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 235: parent 1:235 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
---------------------------------

root@dd-wrt:~# tc -s qdisc ls dev eth0
qdisc pfifo_fast 0: root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
Sent 2261708145 bytes 3827251 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
--------------------------------

root@dd-wrt:~# tc -s qdisc ls dev eth1
qdisc pfifo_fast 0: root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
Sent 4076809671 bytes 2935658 pkt (dropped 0, overlimits 0 requeues 3)
backlog 0b 0p requeues 3
--------------------------------

root@dd-wrt:~# tc -s qdisc show
qdisc pfifo_fast 0: dev eth0 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
Sent 2261778319 bytes 3827644 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc pfifo_fast 0: dev eth1 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
Sent 4076829713 bytes 2935700 pkt (dropped 0, overlimits 0 requeues 3)
backlog 0b 0p requeues 3
qdisc htb 1: dev vlan2 root refcnt 2 r2q 10 default 30 direct_packets_stat 0
Sent 2521566 bytes 8595 pkt (dropped 476, overlimits 872 requeues 0)
backlog 0b 0p requeues 0
qdisc htb 1: dev imq0 root refcnt 2 r2q 10 default 30 direct_packets_stat 0
Sent 10509573 bytes 9015 pkt (dropped 0, overlimits 8079 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 100: dev imq0 parent 1:100 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 10: dev imq0 parent 1:10 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 20: dev imq0 parent 1:20 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 30: dev imq0 parent 1:30 [Unknown qdisc, optlen=48]
Sent 444229 bytes 884 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 40: dev imq0 parent 1:40 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 211: dev imq0 parent 1:211 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 212: dev imq0 parent 1:212 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 213: dev imq0 parent 1:213 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 214: dev imq0 parent 1:214 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 215: dev imq0 parent 1:215 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 221: dev imq0 parent 1:221 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 222: dev imq0 parent 1:222 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 223: dev imq0 parent 1:223 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 224: dev imq0 parent 1:224 [Unknown qdisc, optlen=48]
Sent 10065344 bytes 8131 pkt (dropped 366, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 225: dev imq0 parent 1:225 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 231: dev imq0 parent 1:231 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 232: dev imq0 parent 1:232 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 233: dev imq0 parent 1:233 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 234: dev imq0 parent 1:234 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc fq_codel 235: dev imq0 parent 1:235 [Unknown qdisc, optlen=48]
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0
qdisc pfifo_fast 0: dev imq1 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
backlog 0b 0p requeues 0

I didn't copy the output of when I used just htb/sfq or hsfc/sfq but I did notice that they loaded properly but the problem still that my ingress wasn't properly being handle as I thought to be as it just hung around to 57mbps these test I performed were on a gigabyte laptop connected directly to the router, the router performed perfectly and is able to achieve the said bandwidth from the ISP as they give those extra download/upload bandwidth. I also did these tests on the stock and if performed well just the qos doesn't control download but It still performed as it should have to what the ISP is sending to their transparent emta telephony. I kinda looking for someone else to look into and post an output of their traffic output of a build in the broadcom k3x mega build if you or were having the same type of problem with qos. I'm going to do the same test on the k2.6 build today and post some of those results since they do no obviously don't have the codel/fq_codel built into them and knowing that shouldn't have any influence on the performance of qos in slightest. This is just something that has kinda been puzzling even though you may say it's a under powered soho and could say yes to that only that I'm not on a network that is demanding on anything other than just web browsing, some xbox/ps gaming, no torrents, no proxy, no vpn, nothing to kill a small routers performance just to enable Qos, and I had installed lede/openwrt before and used some those sqm scripts fq_codel/ simple.qos or cake/piece of cake with a positive results of course they don't have wifi but it was all for testing performance anyways. Thank you for reading this long post and I apologize if I placed this post into here as I was wanting to make aware of this issue and some results of type of testing with the hours that it took.


I know there is a thread on a subject about the question and performance issue, with the overall conclusion is it can't handle that much bandwidth in that direction as opposed to egress but this is how it is, or since then changes happened that it won't work properly with older cpu models, not sure of but ok, but I had thought it could have been done none the less to see a better output of bandwidth using dd-wrt qos htb/fq_codel but they work hard as is but maybe have a look at the traffic control output they don't load properly when in use or enabled.
native_tx
DD-WRT User


Joined: 26 Feb 2014
Posts: 122
Location: Texas

PostPosted: Sun Dec 17, 2017 16:52    Post subject: dd-wrt.v24-34080_NEWD-2_K3.x_mega-e3200.bin Reply with quote
Yes is it normal for vpn modules to load and run when they are disabled in Gui? as I'm not using vpn for my network, I know that when using ssh can lead to some issues with performance, but there is an occurrences when after I setup and use https, when I'm using both ssh to allow the gui to enable the performance somehow to cause issues when running speed test, but when disabling the gui access and closing ssh the performance is restored. Qos still doesn't load correctly when i look at it through ssh using tc -s qdisc on both eth0 or imq0 with that being said qos can achieve a A on bufferbloat with A+ on both quality and speed, but in order to achieve that is to have 80% of ingress and 75% egress no priorities set for tcp, while setting up qos i see that when using ports for my ps3 for gaming will load but I don't see them related to the ps3 although they are there the ports and ps3 but the ps3 isn't listed in the destination, it has nothing in destination no ip or mac, as when I look at it through the iptables -t mangle -vnL, the ps3 is static and in the mac address portion of Qos were it's suppose to have priority. Wifi seems to be working as expected although throughput is something I'm experimenting with to find the right txpwr1 and placing number 4 in wl interference for bettering the signals has been proved better for my home not sure if the auto mode was doing as intended but seemed ok. My bandwidth has changed to a different provider as it's fiber again and not cable no docsis 3 connections but my router is able to handle my network, and the dd-wrt firmware i'm finding to optimize it more and more to fit my needs as we are all suppose to find out what works and what doesn't so reading the wiki's provided by dd-wrt helps a great deal but also needs to be updated to stay current to todays situations as some things have obvious changed in firmware that affects performance either positive or negatively.
steve2470
DD-WRT Novice


Joined: 04 Sep 2014
Posts: 7
Location: Orlando, FL, USA

PostPosted: Sat Dec 30, 2017 20:37    Post subject: got r34311 (big) running on my Asus RT-N16 Reply with quote
v3.0-r34311 big (12/29/17)

kinda proud that I got it to run after much work Smile



This is as expected Very Happy Wifi is working perfectly so far as well!

Here is the order of my builds:

1- https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2010/08-12-10-r14929/broadcom_K26/dd-wrt.v24-14929_NEWD-2_K2.6_mini_RT-N16.trx

2- ftp://ftp.dd-wrt.com/betas/2017/12-29-2017-r34311/broadcom/dd-wrt.v24_mini_asus.trx

3- ftp://ftp.dd-wrt.com/betas/2017/12-29-2017-r34311/broadcom_K3X/dd-wrt.v24-34311_NEWD-2_K3.x_mega_RT-N16.trx

4- https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2017/12-29-2017-r34311/broadcom_K3X/dd-wrt.v24-34311_NEWD-2_K3.x-big-RT-N16.trx

_________________
I have been interested in DD-WRT for years but still consider myself a newb.
Current configuration:
Asus RT-N16
v3.0-r34311 big (12/29/17)
Linux 3.10.108 #17150
Broadcom BCM4716 chip rev. 1
dk55
DD-WRT Novice


Joined: 09 Dec 2017
Posts: 3

PostPosted: Fri Mar 02, 2018 1:49    Post subject: Re: Broadcom K3.X testing, test users wanted Reply with quote
Hi,
E2000 / BCM4716 chip rev 1.

I've moved to "DD-WRT v3.0-r35034 mega (02/17/18)" yesterday and I'm happy about move.
Previously installed "dd-wrt.v24-34578_NEWD-2_K3.x_mega-e2000" became very unstable.

In r34578 I encountered following problems:
- the device came to resetting itself spontaneously several times a day, sometimes just minutes after the previous time
- remote syslog (written on NAS) did not reveal source of the problem, but contributed to increased load of the device.
- Status>Router>Network>ActiveIPConnections opened new window but after listing first 50-80 entries httpd died/restarted every time I've tried. Web interface was unavailable for a while after each try. This was also encountered on r34111 and probably on r28647.
- CPU Temperature was often not available
- I have impression that mount.cifs did not work properly with NAS's shares (in r34111 worked ok, somehow in r34578 were broken)


With r35034 is seems that most of these problems are gone.
While I'm reluctant to test remote syslog again, current config works/did not reboot for over 24hrs.
Displays even 800 active connections without complaint. Temperature is displayed.
I'm yet to test mount.cifs.

Anyway, thanks for good work on this release. With r34578 I was already afraid my hardware was nearly dead.
Goto page Previous  1, 2, 3 ... , 54, 55, 56  Next Display posts from previous:    Page 55 of 56
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum