What's new

[Fork] FlexQoS - Flexible QoS Enhancement Script for Adaptive QoS

Vexira

Part of the Furniture
I've been spending a lot of time reading about HTB and fq_codel ("the classics" in the age of CAKE). I was always happy to ignore the complexity of the device priority classes lurking beneath the more pleasant "Category" classes that we usually talk about (Net Control, Work-From-Home, Streaming, etc.). It's quite a fascinating subject, technically and one that can blow your mind especially when trying to unravel the Adaptive QoS classes, qdiscs and filters.

For anyone with more than 10 devices on their network, and who do not use any form of device priority on the Bandwidth Monitor tab of the QoS webUI, I'm interested to know the output of this command on your router:
Code:
tc class show dev br0 | grep -E "parent 10:1 .* prio "
I personally have no device priorities assigned (everything is Default) but I still see some devices assigned to classes that are at prio 3, when everything else is at prio 2.
Code:
# tc class show dev br0 | grep -E "parent 10:1 .* prio "
class htb 10:2 parent 10:1 leaf 1002: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:3 parent 10:1 leaf 1003: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:4 parent 10:1 leaf 1004: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:5 parent 10:1 leaf 1005: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:6 parent 10:1 leaf 1006: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:7 parent 10:1 leaf 1007: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:8 parent 10:1 leaf 1008: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:9 parent 10:1 leaf 1009: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:11 parent 10:1 leaf 1011: prio 3 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:10 parent 10:1 leaf 1010: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:256 parent 10:1 leaf 1256: prio 3 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:13 parent 10:1 leaf 1013: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:12 parent 10:1 leaf 1012: prio 3 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:14 parent 10:1 leaf 1014: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
I can't tell yet if this is an issue that requires a reboot (I had tested a device priority to see what happens underneath the covers, but reverted my change). So is this a flaw in Trend's kernel module that assigns some default priority devices a lower priority class (not all same-priority devices are created equally)?

Anyhow, my latest quest is to see if there's a way to understand and make better use of the device priority structure in Adaptive QoS, which has always been poo-poo'd by FreshJR.

Also, as I've been reading and studying more, I did become quite dismayed at just how old the Linux kernel is on my AC68U. I think I measured the sch_htb.c file from circa January 2010. The more you learn about the latest advances in traffic control, the more you want to play with the latest ideas (e.g. CAKE). OpenWRT is where it's at for CAKE, but I don't really like (or maybe understand?) the best HW options. It becomes rather frustrating to keep trying to crack the Adaptive QoS code (figuratively) when so many other QoS solutions are more "open".

Anyway, I'm not going anywhere anytime soon, but it gets rather lonely trying to unravel this in a vacuum. If anyone is seriously interested in how it all works, I've also started reading the archives of the Bufferbloat mailing list. Especially you CAKE users. You can pick the brains of the authors and other smart people, if you can formulate an intelligent enough question to catch their attention. ;)
ASUSWRT-Merlin RT-AX88U 384.19_0 Fri Aug 14 19:20:07 UTC 2020
[email protected]:/tmp/home/root# tc class show dev br0 | grep -E "parent 10:
1 .* prio "
class htb 10:2 parent 10:1 leaf 1002: prio 3 rate 16Kbit overhead 19 ceil 97280K bit burst 3200b cburst 121600b
class htb 10:3 parent 10:1 leaf 1003: prio 3 rate 16Kbit overhead 19 ceil 97280K bit burst 3200b cburst 121600b
class htb 10:4 parent 10:1 leaf 1004: prio 3 rate 16Kbit overhead 19 ceil 97280K bit burst 3200b cburst 121600b
class htb 10:5 parent 10:1 leaf 1005: prio 3 rate 16Kbit overhead 19 ceil 97280K bit burst 3200b cburst 121600b
class htb 10:6 parent 10:1 leaf 1006: prio 3 rate 16Kbit overhead 19 ceil 97280K bit burst 3200b cburst 121600b
class htb 10:7 parent 10:1 leaf 1007: prio 2 rate 16Kbit overhead 19 ceil 97280K bit burst 3200b cburst 121600b
class htb 10:8 parent 10:1 leaf 1008: prio 2 rate 16Kbit overhead 19 ceil 97280K bit burst 3200b cburst 121600b
class htb 10:9 parent 10:1 leaf 1009: prio 2 rate 16Kbit overhead 19 ceil 97280K bit burst 3200b cburst 121600b
class htb 10:256 parent 10:1 leaf 1256: prio 3 rate 16Kbit overhead 19 ceil 9728 0Kbit burst 3200b cburst 121600b
class htb 10:10 parent 10:1 leaf 1010: prio 2 rate 16Kbit overhead 19 ceil 97280 Kbit burst 3200b cburst 121600b
class htb 10:13 parent 10:1 leaf 1013: prio 3 rate 16Kbit overhead 19 ceil 97280 Kbit burst 3200b cburst 121600b
class htb 10:12 parent 10:1 leaf 1012: prio 2 rate 16Kbit overhead 19 ceil 97280 Kbit burst 3200b cburst 121600b
class htb 10:14 parent 10:1 leaf 1014: prio 2 rate 16Kbit overhead 19 ceil 97280 Kbit burst 3200b cburst 121600b


Ive read about cake and htb also hsbc, for years i wondered what an alternative to htb would be like performance wise in adaptive qos, when i first heard of cake it peaked my interest, since i was running an adsl2+ connection and wanted lower latency in general since when i used Netgear's implementation of FQ_Codel which i think uses qualcom stream burst, i was getting 12ms is most games.

At the moment im wating till adaptive qos adpots a more native form of FQ_Codel which I heard may become a reality after the new ai Mesh update or Cake, which is better for most connections in general.
 

chris.at

Regular Contributor
Here is the output you requested Dave:
ASUSWRT-Merlin RT-AC68U 384.19_0 Fri Aug 14 19:17:44 UTC 2020
[email protected]:/tmp/home/root# tc class show dev br0 | grep -E "parent 10:1 .* prio "
class htb 10:2 parent 10:1 leaf 1002: prio 2 rate 16Kbit overhead 4 ceil 81920Kbit burst 3200b cburst 100Kb
class htb 10:3 parent 10:1 leaf 1003: prio 2 rate 16Kbit overhead 4 ceil 81920Kbit burst 3200b cburst 100Kb
class htb 10:4 parent 10:1 leaf 1004: prio 2 rate 16Kbit overhead 4 ceil 81920Kbit burst 3200b cburst 100Kb
class htb 10:5 parent 10:1 leaf 1005: prio 2 rate 16Kbit overhead 4 ceil 81920Kbit burst 3200b cburst 100Kb
class htb 10:6 parent 10:1 leaf 1006: prio 3 rate 16Kbit overhead 4 ceil 81920Kbit burst 3200b cburst 100Kb
class htb 10:7 parent 10:1 leaf 1007: prio 3 rate 16Kbit overhead 4 ceil 81920Kbit burst 3200b cburst 100Kb
class htb 10:8 parent 10:1 leaf 1008: prio 3 rate 16Kbit overhead 4 ceil 81920Kbit burst 3200b cburst 100Kb
class htb 10:9 parent 10:1 leaf 1009: prio 3 rate 16Kbit overhead 4 ceil 81920Kbit burst 3200b cburst 100Kb
class htb 10:11 parent 10:1 leaf 1011: prio 2 rate 16Kbit overhead 4 ceil 81920Kbit burst 3200b cburst 100Kb
class htb 10:10 parent 10:1 leaf 1010: prio 3 rate 16Kbit overhead 4 ceil 81920Kbit burst 3200b cburst 100Kb
class htb 10:256 parent 10:1 leaf 1256: prio 3 rate 16Kbit overhead 4 ceil 81920Kbit burst 3200b cburst 100Kb
class htb 10:13 parent 10:1 leaf 1013: prio 2 rate 16Kbit overhead 4 ceil 81920Kbit burst 3200b cburst 100Kb
class htb 10:12 parent 10:1 leaf 1012: prio 3 rate 16Kbit overhead 4 ceil 81920Kbit burst 3200b cburst 100Kb
class htb 10:15 parent 10:1 leaf 1015: prio 2 rate 16Kbit overhead 4 ceil 81920Kbit burst 3200b cburst 100Kb
class htb 10:14 parent 10:1 leaf 1014: prio 3 rate 16Kbit overhead 4 ceil 81920Kbit burst 3200b cburst 100Kb
class htb 10:17 parent 10:1 leaf 1017: prio 2 rate 16Kbit overhead 4 ceil 81920Kbit burst 3200b cburst 100Kb
class htb 10:19 parent 10:1 leaf 1019: prio 2 rate 16Kbit overhead 4 ceil 81920Kbit burst 3200b cburst 100Kb
 

TheLyppardMan

Very Senior Member
Interpretation of the spdMerlin results when using Traditional QoS and FlexQoS: I'm just wondering what can be deduced if anything, e.g., do the FlexQoS results indicate that it is working better or worse than Traditional QoS? The first part of the 7-day graph is the Traditional QoS and as you can see, there is a very noticeable difference from when I swapped over to FlexQoS. The second graph just shows the last 24 hours using FlexQoS. Note: In both cases I had the download/upload speeds set to 55 & 13 respectively.
 

Attachments

Bensam123

Occasional Visitor
I've been spending a lot of time reading about HTB and fq_codel ("the classics" in the age of CAKE). I was always happy to ignore the complexity of the device priority classes lurking beneath the more pleasant "Category" classes that we usually talk about (Net Control, Work-From-Home, Streaming, etc.). It's quite a fascinating subject, technically and one that can blow your mind especially when trying to unravel the Adaptive QoS classes, qdiscs and filters.

For anyone with more than 10 devices on their network, and who do not use any form of device priority on the Bandwidth Monitor tab of the QoS webUI, I'm interested to know the output of this command on your router:
Code:
tc class show dev br0 | grep -E "parent 10:1 .* prio "
I personally have no device priorities assigned (everything is Default) but I still see some devices assigned to classes that are at prio 3, when everything else is at prio 2.
Code:
# tc class show dev br0 | grep -E "parent 10:1 .* prio "
class htb 10:2 parent 10:1 leaf 1002: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:3 parent 10:1 leaf 1003: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:4 parent 10:1 leaf 1004: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:5 parent 10:1 leaf 1005: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:6 parent 10:1 leaf 1006: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:7 parent 10:1 leaf 1007: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:8 parent 10:1 leaf 1008: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:9 parent 10:1 leaf 1009: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:11 parent 10:1 leaf 1011: prio 3 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:10 parent 10:1 leaf 1010: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:256 parent 10:1 leaf 1256: prio 3 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:13 parent 10:1 leaf 1013: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:12 parent 10:1 leaf 1012: prio 3 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:14 parent 10:1 leaf 1014: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
I can't tell yet if this is an issue that requires a reboot (I had tested a device priority to see what happens underneath the covers, but reverted my change). So is this a flaw in Trend's kernel module that assigns some default priority devices a lower priority class (not all same-priority devices are created equally)?

Anyhow, my latest quest is to see if there's a way to understand and make better use of the device priority structure in Adaptive QoS, which has always been poo-poo'd by FreshJR.

Also, as I've been reading and studying more, I did become quite dismayed at just how old the Linux kernel is on my AC68U. I think I measured the sch_htb.c file from circa January 2010. The more you learn about the latest advances in traffic control, the more you want to play with the latest ideas (e.g. CAKE). OpenWRT is where it's at for CAKE, but I don't really like (or maybe understand?) the best HW options. It becomes rather frustrating to keep trying to crack the Adaptive QoS code (figuratively) when so many other QoS solutions are more "open".

Anyway, I'm not going anywhere anytime soon, but it gets rather lonely trying to unravel this in a vacuum. If anyone is seriously interested in how it all works, I've also started reading the archives of the Bufferbloat mailing list. Especially you CAKE users. You can pick the brains of the authors and other smart people, if you can formulate an intelligent enough question to catch their attention. ;)
There is Cake for newer Asus routers. I'm still using this over Cake particularly because Cake is fair and I don't want fair, I want a hierarchy of bandwidth, specifically priority. As such I want gaming devices/traffic to always take priority over everything else and slot in VOIP above that. Asus is the only router AFAIK with adaptive QoS in that Microtrend automatically updates the definition and keeps mainly up to date with games that are constantly being released. This takes a lot of work out of my hands of having to manually find ports and assign them a category and of course that's if all the ports are correct and they give you all the ports (that's not always the case).

The only way around that is just assigning a port/mac/IP to a certain priority, however that's less elegant and there is some traffic I don't care about from gaming devices that doesn't need priority at all. And in the case of FlexQoS/Fresh, causes the traffic to become extremely sporadic and wonky (haven't checked 1.0.1)

This goes even deeper. I've been looking into DSCP and there is a lot of conflicting information on whether or not it even does anything, more complicated solutions remark traffic before and after the router as well. Sadly there is almost no routers, specifically home devices which do DSCP. Setting up DSCP also gets extremely complicated extremely fast.

Megathreads here:

Asus could do this too as well when it detects the packets to change the DSCP level as well, but I'm pretty sure it doesn't do that.
 

geobernd

Occasional Visitor
For anyone with more than 10 devices on their network, and who do not use any form of device priority on the Bandwidth Monitor tab of the QoS webUI, I'm interested to know the output of this command on your router:
I personally have no device priorities assigned (everything is Default) but I still see some devices assigned to classes that are at prio 3, when everything else is at prio 2.
I can't tell yet if this is an issue that requires a reboot (I had tested a device priority to see what happens underneath the covers, but reverted my change). So is this a flaw in Trend's kernel module that assigns some default priority devices a lower priority class (not all same-priority devices are created equally)?
I see a mix of prio 3 and 2 entries. No device priority set (double checked just now) and no settings changes at all since the last reboot...

Code:
[email protected]:/tmp/home/root# tc class show dev br0 | grep -E "parent 10:1 .* prio "
class htb 10:2 parent 10:1 leaf 1002: prio 2 rate 16Kbit overhead 18 ceil 118784Kbit burst 3200b cburst 147173b
class htb 10:3 parent 10:1 leaf 1003: prio 3 rate 16Kbit overhead 18 ceil 118784Kbit burst 3200b cburst 147173b
class htb 10:4 parent 10:1 leaf 1004: prio 3 rate 16Kbit overhead 18 ceil 118784Kbit burst 3200b cburst 147173b
class htb 10:5 parent 10:1 leaf 1005: prio 3 rate 16Kbit overhead 18 ceil 118784Kbit burst 3200b cburst 147173b
class htb 10:6 parent 10:1 leaf 1006: prio 2 rate 16Kbit overhead 18 ceil 118784Kbit burst 3200b cburst 147173b
class htb 10:7 parent 10:1 leaf 1007: prio 3 rate 16Kbit overhead 18 ceil 118784Kbit burst 3200b cburst 147173b
class htb 10:8 parent 10:1 leaf 1008: prio 2 rate 16Kbit overhead 18 ceil 118784Kbit burst 3200b cburst 147173b
class htb 10:9 parent 10:1 leaf 1009: prio 2 rate 16Kbit overhead 18 ceil 118784Kbit burst 3200b cburst 147173b
class htb 10:11 parent 10:1 leaf 1011: prio 2 rate 16Kbit overhead 18 ceil 118784Kbit burst 3200b cburst 147173b
class htb 10:256 parent 10:1 leaf 1256: prio 3 rate 16Kbit overhead 18 ceil 118784Kbit burst 3200b cburst 147173b
class htb 10:10 parent 10:1 leaf 1010: prio 2 rate 16Kbit overhead 18 ceil 118784Kbit burst 3200b cburst 147173b
class htb 10:13 parent 10:1 leaf 1013: prio 2 rate 16Kbit overhead 18 ceil 118784Kbit burst 3200b cburst 147173b
class htb 10:12 parent 10:1 leaf 1012: prio 2 rate 16Kbit overhead 18 ceil 118784Kbit burst 3200b cburst 147173b
class htb 10:15 parent 10:1 leaf 1015: prio 3 rate 16Kbit overhead 18 ceil 118784Kbit burst 3200b cburst 147173b
class htb 10:16 parent 10:1 leaf 1016: prio 3 rate 16Kbit overhead 18 ceil 118784Kbit burst 3200b cburst 147173b
 

Maloon

Occasional Visitor
For anyone with more than 10 devices on their network, and who do not use any form of device priority on the Bandwidth Monitor tab of the QoS webUI, I'm interested to know the output of this command on your router:
Code:
tc class show dev br0 | grep -E "parent 10:1 .* prio "
@dave14305 FYI

45 devices. FlexQoS v1.0.2:
Code:
[email protected]:/tmp/home/root# tc class show dev br0 | grep -E "parent 10:1 .* prio "
class htb 10:20 parent 10:1 leaf 1020: prio 3 rate 16Kbit ceil 307200Kbit burst 3200b cburst 375Kb
class htb 10:2 parent 10:1 leaf 1002: prio 2 rate 16Kbit ceil 307200Kbit burst 3200b cburst 375Kb
class htb 10:3 parent 10:1 leaf 1003: prio 2 rate 16Kbit ceil 307200Kbit burst 3200b cburst 375Kb
class htb 10:4 parent 10:1 leaf 1004: prio 2 rate 16Kbit ceil 307200Kbit burst 3200b cburst 375Kb
class htb 10:5 parent 10:1 leaf 1005: prio 2 rate 16Kbit ceil 307200Kbit burst 3200b cburst 375Kb
class htb 10:6 parent 10:1 leaf 1006: prio 2 rate 16Kbit ceil 307200Kbit burst 3200b cburst 375Kb
class htb 10:7 parent 10:1 leaf 1007: prio 3 rate 16Kbit ceil 307200Kbit burst 3200b cburst 375Kb
class htb 10:8 parent 10:1 leaf 1008: prio 3 rate 16Kbit ceil 307200Kbit burst 3200b cburst 375Kb
class htb 10:9 parent 10:1 leaf 1009: prio 2 rate 16Kbit ceil 307200Kbit burst 3200b cburst 375Kb
class htb 10:11 parent 10:1 leaf 1011: prio 2 rate 16Kbit ceil 307200Kbit burst 3200b cburst 375Kb
class htb 10:256 parent 10:1 leaf 1256: prio 3 rate 16Kbit ceil 307200Kbit burst 3200b cburst 375Kb
class htb 10:10 parent 10:1 leaf 1010: prio 2 rate 16Kbit ceil 307200Kbit burst 3200b cburst 375Kb
class htb 10:13 parent 10:1 leaf 1013: prio 2 rate 16Kbit ceil 307200Kbit burst 3200b cburst 375Kb
class htb 10:12 parent 10:1 leaf 1012: prio 3 rate 16Kbit ceil 307200Kbit burst 3200b cburst 375Kb
class htb 10:15 parent 10:1 leaf 1015: prio 3 rate 16Kbit ceil 307200Kbit burst 3200b cburst 375Kb
class htb 10:14 parent 10:1 leaf 1014: prio 3 rate 16Kbit ceil 307200Kbit burst 3200b cburst 375Kb
class htb 10:17 parent 10:1 leaf 1017: prio 3 rate 16Kbit ceil 307200Kbit burst 3200b cburst 375Kb
class htb 10:16 parent 10:1 leaf 1016: prio 3 rate 16Kbit ceil 307200Kbit burst 3200b cburst 375Kb
class htb 10:19 parent 10:1 leaf 1019: prio 2 rate 16Kbit ceil 307200Kbit burst 3200b cburst 375Kb
class htb 10:18 parent 10:1 leaf 1018: prio 3 rate 16Kbit ceil 307200Kbit burst 3200b cburst 375Kb
 

Zavar

New Around Here
Hi Folks. I've been running Flex for a short while and it's been great. I've seen several mentions of TrendMicro, I have all of the Trend stuff turned off in the GUI. Is there something I should have enabled to ensure Flex works properly?
 

dave14305

Part of the Furniture
Hi Folks. I've been running Flex for a short while and it's been great. I've seen several mentions of TrendMicro, I have all of the Trend stuff turned off in the GUI. Is there something I should have enabled to ensure Flex works properly?
When you enable Adaptive QoS, the necessary Trend Micro components will also be enabled (independent of AiProtection).
 

tmcb82

Occasional Visitor
I've been spending a lot of time reading about HTB and fq_codel ("the classics" in the age of CAKE). I was always happy to ignore the complexity of the device priority classes lurking beneath the more pleasant "Category" classes that we usually talk about (Net Control, Work-From-Home, Streaming, etc.). It's quite a fascinating subject, technically and one that can blow your mind especially when trying to unravel the Adaptive QoS classes, qdiscs and filters.

For anyone with more than 10 devices on their network, and who do not use any form of device priority on the Bandwidth Monitor tab of the QoS webUI, I'm interested to know the output of this command on your router:
Code:
tc class show dev br0 | grep -E "parent 10:1 .* prio "
I personally have no device priorities assigned (everything is Default) but I still see some devices assigned to classes that are at prio 3, when everything else is at prio 2.
Code:
# tc class show dev br0 | grep -E "parent 10:1 .* prio "
class htb 10:2 parent 10:1 leaf 1002: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:3 parent 10:1 leaf 1003: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:4 parent 10:1 leaf 1004: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:5 parent 10:1 leaf 1005: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:6 parent 10:1 leaf 1006: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:7 parent 10:1 leaf 1007: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:8 parent 10:1 leaf 1008: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:9 parent 10:1 leaf 1009: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:11 parent 10:1 leaf 1011: prio 3 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:10 parent 10:1 leaf 1010: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:256 parent 10:1 leaf 1256: prio 3 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:13 parent 10:1 leaf 1013: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:12 parent 10:1 leaf 1012: prio 3 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:14 parent 10:1 leaf 1014: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
I can't tell yet if this is an issue that requires a reboot (I had tested a device priority to see what happens underneath the covers, but reverted my change). So is this a flaw in Trend's kernel module that assigns some default priority devices a lower priority class (not all same-priority devices are created equally)?

Anyhow, my latest quest is to see if there's a way to understand and make better use of the device priority structure in Adaptive QoS, which has always been poo-poo'd by FreshJR.

Also, as I've been reading and studying more, I did become quite dismayed at just how old the Linux kernel is on my AC68U. I think I measured the sch_htb.c file from circa January 2010. The more you learn about the latest advances in traffic control, the more you want to play with the latest ideas (e.g. CAKE). OpenWRT is where it's at for CAKE, but I don't really like (or maybe understand?) the best HW options. It becomes rather frustrating to keep trying to crack the Adaptive QoS code (figuratively) when so many other QoS solutions are more "open".

Anyway, I'm not going anywhere anytime soon, but it gets rather lonely trying to unravel this in a vacuum. If anyone is seriously interested in how it all works, I've also started reading the archives of the Bufferbloat mailing list. Especially you CAKE users. You can pick the brains of the authors and other smart people, if you can formulate an intelligent enough question to catch their attention. ;)
I have 23 devices and no changes made to the bandwidth monitor page. I'm using fq_codel and have Learn-From-Home as my lowest priority on A.QOS. This is from a RT-AC68P.

tc class show dev br0 | grep -E "parent 10:
1 .* prio "
class htb 10:22 parent 10:1 leaf 1022: prio 2 rate 16Kbit overhead 18 ceil 174080Kbit burst 3200b cburst 217600b
class htb 10:2 parent 10:1 leaf 1002: prio 2 rate 16Kbit overhead 18 ceil 174080Kbit burst 3200b cburst 217600b
class htb 10:20 parent 10:1 leaf 1020: prio 3 rate 16Kbit overhead 18 ceil 174080Kbit burst 3200b cburst 217600b
class htb 10:3 parent 10:1 leaf 1003: prio 2 rate 16Kbit overhead 18 ceil 174080Kbit burst 3200b cburst 217600b
class htb 10:4 parent 10:1 leaf 1004: prio 3 rate 16Kbit overhead 18 ceil 174080Kbit burst 3200b cburst 217600b
class htb 10:5 parent 10:1 leaf 1005: prio 2 rate 16Kbit overhead 18 ceil 174080Kbit burst 3200b cburst 217600b
class htb 10:6 parent 10:1 leaf 1006: prio 2 rate 16Kbit overhead 18 ceil 174080Kbit burst 3200b cburst 217600b
class htb 10:7 parent 10:1 leaf 1007: prio 2 rate 16Kbit overhead 18 ceil 174080Kbit burst 3200b cburst 217600b
class htb 10:8 parent 10:1 leaf 1008: prio 2 rate 16Kbit overhead 18 ceil 174080Kbit burst 3200b cburst 217600b
class htb 10:11 parent 10:1 leaf 1011: prio 3 rate 16Kbit overhead 18 ceil 174080Kbit burst 3200b cburst 217600b
class htb 10:10 parent 10:1 leaf 1010: prio 2 rate 16Kbit overhead 18 ceil 174080Kbit burst 3200b cburst 217600b
class htb 10:256 parent 10:1 leaf 1256: prio 3 rate 16Kbit overhead 18 ceil 174080Kbit burst 3200b cburst 217600b
class htb 10:13 parent 10:1 leaf 1013: prio 3 rate 16Kbit overhead 18 ceil 174080Kbit burst 3200b cburst 217600b
class htb 10:12 parent 10:1 leaf 1012: prio 2 rate 16Kbit overhead 18 ceil 174080Kbit burst 3200b cburst 217600b
class htb 10:15 parent 10:1 leaf 1015: prio 3 rate 16Kbit overhead 18 ceil 174080Kbit burst 3200b cburst 217600b
class htb 10:14 parent 10:1 leaf 1014: prio 3 rate 16Kbit overhead 18 ceil 174080Kbit burst 3200b cburst 217600b
class htb 10:17 parent 10:1 leaf 1017: prio 3 rate 16Kbit overhead 18 ceil 174080Kbit burst 3200b cburst 217600b
class htb 10:16 parent 10:1 leaf 1016: prio 3 rate 16Kbit overhead 18 ceil 174080Kbit burst 3200b cburst 217600b
class htb 10:19 parent 10:1 leaf 1019: prio 3 rate 16Kbit overhead 18 ceil 174080Kbit burst 3200b cburst 217600b
class htb 10:18 parent 10:1 leaf 1018: prio 3 rate 16Kbit overhead 18 ceil 174080Kbit burst 3200b cburst 217600b
 

chris.at

Regular Contributor
Short question Dave, I tried to configure a wildcard AppDB redirect rule with 1400C* but it won't get accepted. Is this not possible by design or something that's simply just missing in the gui checks?
 

QuikSilver

Very Senior Member

dave14305

Part of the Furniture
Short question Dave, I tried to configure a wildcard AppDB redirect rule with 1400C* but it won't get accepted. Is this not possible by design or something that's simply just missing in the gui checks?
Not implemented. You can only wildcard the whole category 14**** or not at all.
 

rlj2

Occasional Visitor
I've been spending a lot of time reading about HTB and fq_codel ("the classics" in the age of CAKE). I was always happy to ignore the complexity of the device priority classes lurking beneath the more pleasant "Category" classes that we usually talk about (Net Control, Work-From-Home, Streaming, etc.). It's quite a fascinating subject, technically and one that can blow your mind especially when trying to unravel the Adaptive QoS classes, qdiscs and filters.

For anyone with more than 10 devices on their network, and who do not use any form of device priority on the Bandwidth Monitor tab of the QoS webUI, I'm interested to know the output of this command on your router:
Code:
tc class show dev br0 | grep -E "parent 10:1 .* prio "
I personally have no device priorities assigned (everything is Default) but I still see some devices assigned to classes that are at prio 3, when everything else is at prio 2.
Code:
# tc class show dev br0 | grep -E "parent 10:1 .* prio "
class htb 10:2 parent 10:1 leaf 1002: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:3 parent 10:1 leaf 1003: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:4 parent 10:1 leaf 1004: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:5 parent 10:1 leaf 1005: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:6 parent 10:1 leaf 1006: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:7 parent 10:1 leaf 1007: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:8 parent 10:1 leaf 1008: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:9 parent 10:1 leaf 1009: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:11 parent 10:1 leaf 1011: prio 3 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:10 parent 10:1 leaf 1010: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:256 parent 10:1 leaf 1256: prio 3 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:13 parent 10:1 leaf 1013: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:12 parent 10:1 leaf 1012: prio 3 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
class htb 10:14 parent 10:1 leaf 1014: prio 2 rate 16Kbit overhead 18 ceil 322560Kbit burst 3200b cburst 403200b
I can't tell yet if this is an issue that requires a reboot (I had tested a device priority to see what happens underneath the covers, but reverted my change). So is this a flaw in Trend's kernel module that assigns some default priority devices a lower priority class (not all same-priority devices are created equally)?

Anyhow, my latest quest is to see if there's a way to understand and make better use of the device priority structure in Adaptive QoS, which has always been poo-poo'd by FreshJR.

Also, as I've been reading and studying more, I did become quite dismayed at just how old the Linux kernel is on my AC68U. I think I measured the sch_htb.c file from circa January 2010. The more you learn about the latest advances in traffic control, the more you want to play with the latest ideas (e.g. CAKE). OpenWRT is where it's at for CAKE, but I don't really like (or maybe understand?) the best HW options. It becomes rather frustrating to keep trying to crack the Adaptive QoS code (figuratively) when so many other QoS solutions are more "open".

Anyway, I'm not going anywhere anytime soon, but it gets rather lonely trying to unravel this in a vacuum. If anyone is seriously interested in how it all works, I've also started reading the archives of the Bufferbloat mailing list. Especially you CAKE users. You can pick the brains of the authors and other smart people, if you can formulate an intelligent enough question to catch their attention. ;)
class htb 10:2 parent 10:1 leaf 1002: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:3 parent 10:1 leaf 1003: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:4 parent 10:1 leaf 1004: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:5 parent 10:1 leaf 1005: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:6 parent 10:1 leaf 1006: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:7 parent 10:1 leaf 1007: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:8 parent 10:1 leaf 1008: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:9 parent 10:1 leaf 1009: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:11 parent 10:1 leaf 1011: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:10 parent 10:1 leaf 1010: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:13 parent 10:1 leaf 1013: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:12 parent 10:1 leaf 1012: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:15 parent 10:1 leaf 1015: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:14 parent 10:1 leaf 1014: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:17 parent 10:1 leaf 1017: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:16 parent 10:1 leaf 1016: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:19 parent 10:1 leaf 1019: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:18 parent 10:1 leaf 1018: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:22 parent 10:1 leaf 1022: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:23 parent 10:1 leaf 1023: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:20 parent 10:1 leaf 1020: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:21 parent 10:1 leaf 1021: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:26 parent 10:1 leaf 1026: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:27 parent 10:1 leaf 1027: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:24 parent 10:1 leaf 1024: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:25 parent 10:1 leaf 1025: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:28 parent 10:1 leaf 1028: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:29 parent 10:1 leaf 1029: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:33 parent 10:1 leaf 1033: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:32 parent 10:1 leaf 1032: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:256 parent 10:1 leaf 1256: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:31 parent 10:1 leaf 1031: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:30 parent 10:1 leaf 1030: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:35 parent 10:1 leaf 1035: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:34 parent 10:1 leaf 1034: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b

class htb 10:2 parent 10:1 leaf 1002: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
 

dave14305

Part of the Furniture
class htb 10:2 parent 10:1 leaf 1002: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:3 parent 10:1 leaf 1003: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:4 parent 10:1 leaf 1004: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:5 parent 10:1 leaf 1005: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:6 parent 10:1 leaf 1006: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:7 parent 10:1 leaf 1007: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:8 parent 10:1 leaf 1008: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:9 parent 10:1 leaf 1009: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
...
That's interesting that no prio is displayed at all in your output. But it seems like there's no discernable pattern to the prioritization of 2 or 3 for devices supposedly equal in others' output either.
 

rlj2

Occasional Visitor
class htb 10:2 parent 10:1 leaf 1002: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:3 parent 10:1 leaf 1003: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:4 parent 10:1 leaf 1004: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:5 parent 10:1 leaf 1005: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:6 parent 10:1 leaf 1006: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:7 parent 10:1 leaf 1007: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:8 parent 10:1 leaf 1008: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:9 parent 10:1 leaf 1009: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:11 parent 10:1 leaf 1011: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:10 parent 10:1 leaf 1010: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:13 parent 10:1 leaf 1013: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:12 parent 10:1 leaf 1012: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:15 parent 10:1 leaf 1015: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:14 parent 10:1 leaf 1014: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:17 parent 10:1 leaf 1017: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:16 parent 10:1 leaf 1016: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:19 parent 10:1 leaf 1019: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:18 parent 10:1 leaf 1018: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:22 parent 10:1 leaf 1022: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:23 parent 10:1 leaf 1023: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:20 parent 10:1 leaf 1020: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:21 parent 10:1 leaf 1021: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:26 parent 10:1 leaf 1026: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:27 parent 10:1 leaf 1027: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:24 parent 10:1 leaf 1024: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:25 parent 10:1 leaf 1025: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:28 parent 10:1 leaf 1028: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:29 parent 10:1 leaf 1029: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:33 parent 10:1 leaf 1033: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:32 parent 10:1 leaf 1032: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:256 parent 10:1 leaf 1256: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:31 parent 10:1 leaf 1031: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:30 parent 10:1 leaf 1030: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:35 parent 10:1 leaf 1035: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
class htb 10:34 parent 10:1 leaf 1034: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b

class htb 10:2 parent 10:1 leaf 1002: prio rate 16Kbit overhead 27 ceil 25600Kbit burst 3200b cburst 32000b
Mines not showing a prio rate like others?
 

rlj2

Occasional Visitor
That's interesting that no prio is displayed at all in your output. But it seems like there's no discernable pattern to the prioritization of 2 or 3 for devices supposedly equal in others' output either.
Just saw your post , after i replied to mine.. I noticed that also. But dont know what it means. I can tell you I couldnt figure out how to 100% get rid of device priorities I had used before so I did a nvram set qos_rulelist="".. this was the priority that were set. I even set priority to some devices again to make sure thats where they went before I did a commit. Maybe I screwed up?

[email protected]:/tmp/home/root# nvram show|grep qos
size: 68529 bytes (62543 left)
qos_ack=on
qos_atm=
qos_burst0=
qos_burst1=
qos_default=3
qos_enable=1
qos_fin=off
qos_ibw=25600
qos_ibw1=
qos_icmp=on
qos_inuse=29
qos_irates=100,100,100,100,50,0,0,0,0,0
qos_method=0
qos_obw=2048
qos_obw1=
qos_orules=
qos_overhead=27
qos_reset=0
qos_rst=off
qos_ruleset=
qos_sched=2
qos_sticky=1
qos_syn=on
qos_type=1
qos_bw_rulelist=
qos_orates=80-100,10-100,5-100,3-100,2-35,0-0,0-0,0-0,0-0,0-0
qos_rulelist=
 
Last edited:

dave14305

Part of the Furniture
Just saw your post , after i replied to mine.. I noticed that also. But dont know what it means. I can tell you I couldnt figure out how to 100% get rid of device priorities I had used before so I did a nvram set qos_rulelist="".. this was the priority that were set. I even set priority to some devices again to make sure thats where they went before I did a commit. Maybe I screwed up?

[email protected]:/tmp/home/root# nvram show|grep qos
size: 68529 bytes (62543 left)
qos_ack=on
qos_atm=
qos_burst0=
qos_burst1=
qos_default=3
qos_enable=1
qos_fin=off
qos_ibw=25600
qos_ibw1=
qos_icmp=on
qos_inuse=29
qos_irates=100,100,100,100,50,0,0,0,0,0
qos_method=0
qos_obw=2048
qos_obw1=
qos_orules=
qos_overhead=27
qos_reset=0
qos_rst=off
qos_ruleset=
qos_sched=2
qos_sticky=1
qos_syn=on
qos_type=1
qos_bw_rulelist=
qos_orates=80-100,10-100,5-100,3-100,2-35,0-0,0-0,0-0,0-0,0-0
qos_rulelist=
I think you'll want to at least initialize it with the firmware default value again:
Bash:
nvram set qos_rulelist="<Web Surf>>80>tcp>0~512>0<HTTPS>>443>tcp>0~512>0<File Transfer>>80>tcp>512~>3<File Transfer>>443>tcp>512~>3"
nvram commit
service "restart_qos;restart_firewall"
 

rlj2

Occasional Visitor
I think you'll want to at least initialize it with the firmware default value again:
Bash:
nvram set qos_rulelist="<Web Surf>>80>tcp>0~512>0<HTTPS>>443>tcp>0~512>0<File Transfer>>80>tcp>512~>3<File Transfer>>443>tcp>512~>3"
nvram commit
service "restart_qos;restart_firewall"
ill set this right now, but it didnt have those rules before i messed with it, was only devices i had set priorities to
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top