When you say "QoS no longer works for me" do you mean that you get no internet or have like a reduced speed or other?
If you have CTF enabled and you are using QoS then make sure that you all checked in TCP-Packet Priority and then enable Default Bandwidth Level to 100000, save, apply and reboot and test again.
Posted: Sat Jul 28, 2018 20:19 Post subject: Re: QOS problem broadcom_K26
Had to look up CTF (Cut Through Forwarding)
Not sure where that is toggled will go through the menu to look for it.
Since CTF requires old unsupported kernels (2.6, etc) without security fixes/CVE, then does that mean that the newer Netgear Stock firmware (along with Tomato/Vortex) are unsafe/insecure to use because they do not have security patches/fixes installed? Or does Netgear utilize something that DD-WRT community cannot or does not have access to?
kernel 2.6 is EOL so no longer receives upstream kernel patches.
as ctf is a closed source there have not been any security peer reviews.
Anyway back to my issue and testing
STD NoKaid Small
dd-wrt.v24-21061_NEWD-2_K2.6_std_nokaid_small.bin
iptables -t mangle -vnL works, get result in window
QOS working
21061
23503
26138
28444
QOS not working, command iptables still working
29147
30880
QOS not working, command not working screen flash no results
36347
36330
For QOS I am only doing the top part
Start QOS (x) Enable
Port WAN
Packet HTB
Down 20000
Up 3000
Packet priorty
Ack ( ) Syn (x) Fin (x) RST (x)
Apply > Save
Rolling builds back and forth and just changing these settings is all I need to get QOS working.
So I found 4 builds that work with QOS and at some point it stopped then later the commands stopped being functional as well
By QOS not working, I mean that no control is applied, getting full bandwidth no blocking seems to occur.
Trying to narrow down still when it stops working and then will test alternate builds
Yes CTF is Cut Throught Forwarding, sorry for assuming you knew. It should be on the Basic Setup tab on the Setup page.
I am now sure about CTF requiring old kernels because at present i am using BS r34760 with kernel 4.4.114 and it runs fine. Some have experienced CTF having a reaction of "killing" DL speed when you have QoS enabled, i too saw this but this was when i had ACK TCP-Packet Priority unchecked, once i checked it, i got full speeds which is why i asked if you have done so as well eventhough you are having issues. R34760 is from January 2018, there are newer builds with newer kernels that have CTF as well.
36330 is recent.
I noticed you said you apply and save but you said nothing about reboot, you should save, apply then reboot as well. When you do it this way, save---->apply----reboot, make sure to set your DL speed to half just to check if it works then you can put it back to whatever you want.
Posted: Sat Jul 28, 2018 21:29 Post subject: QOS problem broadcom_K26
STD NoKaid Small
dd-wrt.v24-21061_NEWD-2_K2.6_std_nokaid_small.bin
iptables -t mangle -vnL works, get result in window
QOS working
21061
23503
26138
28444
28976
29085
29114 (3728K)
(20k drop in build size after this)
QOS not working, command iptables still working
29134 (3708k)
29147
30880
QOS not working, command not working screen flash no results
36347
36330
Apply > Save (tried reboot as well)
So starting with build 29134 QOS no longer works.
20k drop in package size
QOS enabled seems to no longer have any effect.
I have tried by protocol,mac and user limited ,nothing has any effect after this build number.
Current builds not working either. Guessing it has been an issue for a while and no one must use very often.
Retested 36330 (QOS still no effect, and COMMAND seems to execute but this is broken as mentioned before, no results when execute commands here anymore, used to give results, this must have broken at some point as well in the build process)
would like to know what was left out when the build size dropped 20k in size. may not be relevant but that is all the info i can provide
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Sat Aug 11, 2018 16:09 Post subject:
I think the more recent K2.6 builds, with maybe the exception of 35531, are broke all to hell. I ran down the gamut of K2.6 from 35244 up on webGUI command interface issues and this is a K2.6 build problem
I don't use QoS, so not sure what to tell you, but it just seems that the K2.6 builds are getting mangled all to shit. I would suggest 33722, 35531 up for testing, but honestly, you may want to think about coming over to the dark side (K3x builds) unless you can find a good K2.6 build that is stable and works for you. NOTE: K3x 36527 the commands interface still works fine for me.
Posted: Sat Aug 11, 2018 16:16 Post subject: QOS problem broadcom_K26
I think this is the v3 u are talking about for wrt160 supposed to be same or compatible hw with e1000 v1
dd-wrt.v24-36527_NEWD-2_K2.6_mini_wrt160nv3.bin
I tried this as well same issues, QOS not working, command prompt does not return results.
Flashing to 36079 same issue.
DD-WRT may function ok as a WIFI router or general use but not usable for QOS something seems to be broken going back years.
I know it is an old router, but unless someone goes back and explains why there was a 20k difference in build size starting with build 29114 to 29134 I would say that every build since has been broken regarding QOS and no one has ever tested or had it working since and the command window broke sometime after.
I tried running 29114 for about a week but had to reboot almost daily and wifi was disconnecting repeatedly.
If you got QOS working on a later build please prove me wrong by posting results and verifying command window works.
What command did you use to check your QoS, i use iptables -t nat -L as provided by jwh7 and it shows what was forwarded. You can see my results in previous builds like r36330 located here https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=315911
