What's new

FlexQoS FlexQoS 1.0 - Flexible QoS Enhancement Script for Adaptive QoS

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Latest 384.19 Alpha seems to have broken FlexQos, I was running 0.8.2 and when I flashed the firmware it caused the gui to become unresponsive. I tried rebooting the gui via ssh but no joy. I then noticed there was an update to FlexQos, applied this via ssh and now the gui of the router loads but flexqos seems broken. Nothing is being limited on the downstream at all and downstream traffic does not show on the flexqos tab.

Edit - Might not be flexqos, seems qos is broken full stop. Uninstalled FlexQos, disabled and enabled Qos and it's not limiting anything at all.
 
Last edited:
I dont know if this is something with FlexQoS or Merlin or ASUS. When transferring through VPNC. While incoming traffic via the VPNC the "Bandwidth Monitor" will show it is upload.
I don't know much about running a VPN client on the router, but there are still a couple hard-coded rules from FreshJR that are intended to solve the VPN upload/download problem. I don't know if they work. Run this and see if the OUTPUTs rule and the first POSTROUTING rule have any hits.
Code:
iptables -t mangle -nvL

Code:
iptables_static_rules() {
    echo "Applying iptables static rules"
    iptables -D POSTROUTING -t mangle -o br0 -m mark --mark 0x40000000/0xc0000000 -j MARK --set-xmark 0x80000000/0xC0000000 > /dev/null 2>&1        #VPN Fix - (Fixes download traffic showing up in upload section when router is acting as a VPN Client)
    iptables -A POSTROUTING -t mangle -o br0 -m mark --mark 0x40000000/0xc0000000 -j MARK --set-xmark 0x80000000/0xC0000000
    iptables -D OUTPUT -t mangle -o "$wan" -p udp -m multiport ! --dports 53,123 -j MARK --set-mark ${Downloads_mark_up} > /dev/null 2>&1        #VPN Fix - (Fixes upload traffic not detected when the router is acting as a VPN Client)
    iptables -A OUTPUT -t mangle -o "$wan" -p udp -m multiport ! --dports 53,123 -j MARK --set-mark ${Downloads_mark_up}
    iptables -D OUTPUT -t mangle -o "$wan" -p tcp -m multiport ! --dports 53,123,853 -j MARK --set-mark ${Downloads_mark_up} > /dev/null 2>&1        #VPN Fix - (Fixes upload traffic not detected when the router is acting as a VPN Client)
    iptables -A OUTPUT -t mangle -o "$wan" -p tcp -m multiport ! --dports 53,123,853 -j MARK --set-mark ${Downloads_mark_up}
    if [ "$IPv6_enabled" != "disabled" ]; then
        echo "Applying ip6tables static rules"
        ip6tables -D POSTROUTING -t mangle -o br0 -m mark --mark 0x40000000/0xc0000000 -j MARK --set-xmark 0x80000000/0xC0000000 > /dev/null 2>&1        #VPN Fix - (Fixes download traffic showing up in upload section when router is acting as a VPN Client)
        ip6tables -A POSTROUTING -t mangle -o br0 -m mark --mark 0x40000000/0xc0000000 -j MARK --set-xmark 0x80000000/0xC0000000
        ip6tables -D OUTPUT -t mangle -o "$wan" -p udp -m multiport ! --dports 53,123 -j MARK --set-mark ${Downloads_mark_up} > /dev/null 2>&1        #VPN Fix - (Fixes upload traffic not detected when the router is acting as a VPN Client)
        ip6tables -A OUTPUT -t mangle -o "$wan" -p udp -m multiport ! --dports 53,123 -j MARK --set-mark ${Downloads_mark_up}
        ip6tables -D OUTPUT -t mangle -o "$wan" -p tcp -m multiport ! --dports 53,123,853 -j MARK --set-mark ${Downloads_mark_up} > /dev/null 2>&1        #VPN Fix - (Fixes upload traffic not detected when the router is acting as a VPN Client)
        ip6tables -A OUTPUT -t mangle -o "$wan" -p tcp -m multiport ! --dports 53,123,853 -j MARK --set-mark ${Downloads_mark_up}
    fi
}

Just a quick check, the difference is this between FreshJR and FlexQoS...

"$wan", in the original code its $wan.
Haven't test it yet, still waiting to get home...


UPDATE:
Damn, totally misread the initial post, I run VPN from a client, not the router itself... :rolleyes:
Should not have read technical forums in between transport... :D
So yeah, I think the post from FreshJR should solve it, manually...
 
Last edited:
Code:
iptables_static_rules() {
    echo "Applying iptables static rules"
    iptables -D POSTROUTING -t mangle -o br0 -m mark --mark 0x40000000/0xc0000000 -j MARK --set-xmark 0x80000000/0xC0000000 > /dev/null 2>&1        #VPN Fix - (Fixes download traffic showing up in upload section when router is acting as a VPN Client)
    iptables -A POSTROUTING -t mangle -o br0 -m mark --mark 0x40000000/0xc0000000 -j MARK --set-xmark 0x80000000/0xC0000000
    iptables -D OUTPUT -t mangle -o "$wan" -p udp -m multiport ! --dports 53,123 -j MARK --set-mark ${Downloads_mark_up} > /dev/null 2>&1        #VPN Fix - (Fixes upload traffic not detected when the router is acting as a VPN Client)
    iptables -A OUTPUT -t mangle -o "$wan" -p udp -m multiport ! --dports 53,123 -j MARK --set-mark ${Downloads_mark_up}
    iptables -D OUTPUT -t mangle -o "$wan" -p tcp -m multiport ! --dports 53,123,853 -j MARK --set-mark ${Downloads_mark_up} > /dev/null 2>&1        #VPN Fix - (Fixes upload traffic not detected when the router is acting as a VPN Client)
    iptables -A OUTPUT -t mangle -o "$wan" -p tcp -m multiport ! --dports 53,123,853 -j MARK --set-mark ${Downloads_mark_up}
    if [ "$IPv6_enabled" != "disabled" ]; then
        echo "Applying ip6tables static rules"
        ip6tables -D POSTROUTING -t mangle -o br0 -m mark --mark 0x40000000/0xc0000000 -j MARK --set-xmark 0x80000000/0xC0000000 > /dev/null 2>&1        #VPN Fix - (Fixes download traffic showing up in upload section when router is acting as a VPN Client)
        ip6tables -A POSTROUTING -t mangle -o br0 -m mark --mark 0x40000000/0xc0000000 -j MARK --set-xmark 0x80000000/0xC0000000
        ip6tables -D OUTPUT -t mangle -o "$wan" -p udp -m multiport ! --dports 53,123 -j MARK --set-mark ${Downloads_mark_up} > /dev/null 2>&1        #VPN Fix - (Fixes upload traffic not detected when the router is acting as a VPN Client)
        ip6tables -A OUTPUT -t mangle -o "$wan" -p udp -m multiport ! --dports 53,123 -j MARK --set-mark ${Downloads_mark_up}
        ip6tables -D OUTPUT -t mangle -o "$wan" -p tcp -m multiport ! --dports 53,123,853 -j MARK --set-mark ${Downloads_mark_up} > /dev/null 2>&1        #VPN Fix - (Fixes upload traffic not detected when the router is acting as a VPN Client)
        ip6tables -A OUTPUT -t mangle -o "$wan" -p tcp -m multiport ! --dports 53,123,853 -j MARK --set-mark ${Downloads_mark_up}
    fi
}

Just a quick check, the difference is this between FreshJR and FlexQoS...

"$wan", in the original code its $wan.
Haven't test it yet, still waiting to get home...
The quotes don’t change anything in this scenario. But I did notice that the first 2 statements have been obsolete since 384.8 when Merlin added them to the updown script.

https://github.com/RMerl/asuswrt-me...lease/src/router/others/updown-client.sh#L137

Code:
    iptables -D POSTROUTING -t mangle -o br0 -m mark --mark 0x40000000/0xc0000000 -j MARK --set-xmark 0x80000000/0xC0000000 > /dev/null 2>&1        #VPN Fix - (Fixes download traffic showing up in upload section when router is acting as a VPN Client)
    iptables -A POSTROUTING -t mangle -o br0 -m mark --mark 0x40000000/0xc0000000 -j MARK --set-xmark 0x80000000/0xC0000000
 
@dave14305 I'm still getting the rates error on the new Merlin alpha is there anything you need me to post like an output I seem that it still gets applied but there is some rates required error still.

Ping me for what ever logs of commands you need me to run.
 
@dave14305 I'm still getting the rates error on the new Merlin alpha is there anything you need me to post like an output I seem that it still gets applied but there is some rates required error still.

Ping me for what ever logs of commands you need me to run.
Let’s start with the debug output.
 
Let’s start with the debug output.
Done I'll go bring it up and post the output actually could you please check your pm inbox I think I sent it to you but I'll do it again since the QoS changed.
 
Done I'll go bring it up and post the output actually could you please check your pm inbox I think I sent it to you but I'll do it again since the QoS changed.
Actually, what I want to see is the logfile of this command:
Code:
sh -x /jffs/addons/flexqos/flexqos.sh debug > /tmp/home/root/flex.log 2>&1
 
allegedly the log was to big to post it exceed charter limitations, but here it is:
http://www.mediafire.com/file/9jww5m71bksj9gx/flex.log/file

and this is the error
FlexQoS: "rate" is required
Somehow your bandwidth settings aren't in the custom settings file correctly. I'll suggest an uninstall and reinstall, but before that, please post the output of:
Code:
nvram get fb_comment
nvram get fb_email_dbg
cat /jffs/addons/flexqos/restore_freshjr_nvram.sh
 
Somehow your bandwidth settings aren't in the custom settings file correctly. I'll suggest an uninstall and reinstall, but before that, please post the output of:
Code:
nvram get fb_comment
nvram get fb_email_dbg
cat /jffs/addons/flexqos/restore_freshjr_nvram.sh
ASUSWRT-Merlin RT-AX88U 384.19_alpha1-g9ca4b67bb0 Wed Jul 1 22:58:11 UTC 2020
vexira@RT-AX88U-C528:/tmp/home/root# nvram get fb_comment

vexira@RT-AX88U-C528:/tmp/home/root# nvram get fb_email_dbg

vexira@RT-AX88U-C528:/tmp/home/root# cat /jffs/addons/flexqos/restore_freshjr_nv
ram.sh
nvram set fb_comment=""
nvram set fb_email_dbg=""
nvram commit
vexira@RT-AX88U-C528:/tmp/home/root#

the odd part is it will still say that no mods necessary after or it apply the bandwidth settings
 
@dave14305
I think i know what happened the reinstall must have fixed it after alpha 19 its probably because of the missing categories before, and i upgraded so it must have had the old settings, which causes it to bug out on anything below 384.19 A1.
 
Last edited:
@Vexira Does your Flexqos classification work with the latest 384.19 beta?
FlexQos.png
 
@Vexira Does your Flexqos classification work with the latest 384.19 beta?
FlexQos.png
Good question I just re installed form scratch because of the update and I'm getting the same issue as you on classification and flex with pps I just checked it.
 
@dave14305, I have a strange problem. My routed all traffic via iptables to/from my Aruba (enterprise VPN router) to the Work-from-Home category (screenshot 1) then in AppDB redirected email services and VOIP services (05**** & 06****) to Web Surfing (screenshot 2, to try to keep my Aruba traffic as isolated and high priority as possible). In the tracked connections it indicates the Aruba (192.168.1.101)(screenshot 3) IS being put into the Work-from-Home group BUT in the pie chart (screenshot 4) it seems to indicate it is going to the Web Surfing group NOT Work-from-Home. Then to throw one last curve ball at you I look at the Merlin classification page and it shows the Aruba (192.168.1.101) in the File Transferring category (screenshot 5). What am I missing here?

Code:
ASUSWRT-Merlin RT-AC68U 384.18_0 Sun Jun 28 17:57:07 UTC 2020
tmcb82@RT-AC68U-A7A8:/tmp/home/root# flexqos -debug

FlexQoS v0.8.5 released 07/01/2020

Debug:

Undf Prio: 2
Undf FlowID: 1:15
Classes Present: 8
Down Band: 174080
Up Band  : 9523
***********
Net Control = 1:10
Work-From-Home = 1:11
Gaming = 1:16
Others = 1:15
Web Surfing = 1:13
Streaming = 1:12
Downloads = 1:14
Defaults = 1:17
***********
Downrates -- 8704, 43520, 52224, 26112, 8704, 17408, 8704, 8704
Downceils -- 174080, 174080, 174080, 174080, 174080, 174080, 174080, 174080
Downbursts -- 9596b, 43182b, 20785b, 9592b, 7996b, 6395b, 3197b, 3197b
DownCbursts -- 217600b, 217600b, 217600b, 217600b, 217600b, 217600b, 217600b, 217600b
***********
Uprates -- 476, 3809, 1428, 1237, 476, 1142, 476, 476
Upceils -- 9523, 9523, 9523, 9523, 9523, 9523, 9523, 9523
Upbursts -- 3198b, 3198b, 3198b, 3198b, 3198b, 3198b, 3198b, 3198b
UpCbursts -- 11195b, 11195b, 11195b, 11195b, 11195b, 11195b, 11195b, 11195b
iptables settings: <>>udp>>500,4500>>3<>>udp>16384:16415>>>3<>>tcp>>119,563>>5<>>tcp>>80,443>08****>7<192.168.1.101>>both>>>>3<192.168.1.103/31>>both>>>>2<192.168.1.104>>both>>>>2
iptables -D POSTROUTING -t mangle -o br0   -p udp  -m multiport  --sports 500,4500  -j MARK --set-mark 0x80060001 >/dev/null 2>&1
iptables -A POSTROUTING -t mangle -o br0   -p udp  -m multiport  --sports 500,4500  -j MARK --set-mark 0x80060001
iptables -D POSTROUTING -t mangle -o eth0   -p udp  -m multiport  --dports 500,4500  -j MARK --set-mark 0x40060001 >/dev/null 2>&1
iptables -A POSTROUTING -t mangle -o eth0   -p udp  -m multiport  --dports 500,4500  -j MARK --set-mark 0x40060001
iptables -D POSTROUTING -t mangle -o br0   -p udp  --dport 16384:16415   -j MARK --set-mark 0x80060001 >/dev/null 2>&1
iptables -A POSTROUTING -t mangle -o br0   -p udp  --dport 16384:16415   -j MARK --set-mark 0x80060001
iptables -D POSTROUTING -t mangle -o eth0   -p udp  --sport 16384:16415   -j MARK --set-mark 0x40060001 >/dev/null 2>&1
iptables -A POSTROUTING -t mangle -o eth0   -p udp  --sport 16384:16415   -j MARK --set-mark 0x40060001
iptables -D POSTROUTING -t mangle -o br0   -p tcp  -m multiport  --sports 119,563  -j MARK --set-mark 0x80030001 >/dev/null 2>&1
iptables -A POSTROUTING -t mangle -o br0   -p tcp  -m multiport  --sports 119,563  -j MARK --set-mark 0x80030001
iptables -D POSTROUTING -t mangle -o eth0   -p tcp  -m multiport  --dports 119,563  -j MARK --set-mark 0x40030001 >/dev/null 2>&1
iptables -A POSTROUTING -t mangle -o eth0   -p tcp  -m multiport  --dports 119,563  -j MARK --set-mark 0x40030001
iptables -D POSTROUTING -t mangle -o br0   -p tcp  -m multiport  --sports 80,443 -m mark --mark 0x80080000/0xc03f0000 -j MARK --set-mark 0x803f0001 >/dev/null 2>&1
iptables -A POSTROUTING -t mangle -o br0   -p tcp  -m multiport  --sports 80,443 -m mark --mark 0x80080000/0xc03f0000 -j MARK --set-mark 0x803f0001
iptables -D POSTROUTING -t mangle -o eth0   -p tcp  -m multiport  --dports 80,443 -m mark --mark 0x40080000/0xc03f0000 -j MARK --set-mark 0x403f0001 >/dev/null 2>&1
iptables -A POSTROUTING -t mangle -o eth0   -p tcp  -m multiport  --dports 80,443 -m mark --mark 0x40080000/0xc03f0000 -j MARK --set-mark 0x403f0001
iptables -D POSTROUTING -t mangle -o br0  -d 192.168.1.101      -j MARK --set-mark 0x80060001 >/dev/null 2>&1
iptables -A POSTROUTING -t mangle -o br0  -d 192.168.1.101      -j MARK --set-mark 0x80060001
iptables -D POSTROUTING -t mangle -o eth0  -s 192.168.1.101      -j MARK --set-mark 0x40060001 >/dev/null 2>&1
iptables -A POSTROUTING -t mangle -o eth0  -s 192.168.1.101      -j MARK --set-mark 0x40060001
iptables -D POSTROUTING -t mangle -o br0  -d 192.168.1.103/31      -j MARK --set-mark 0x80040001 >/dev/null 2>&1
iptables -A POSTROUTING -t mangle -o br0  -d 192.168.1.103/31      -j MARK --set-mark 0x80040001
iptables -D POSTROUTING -t mangle -o eth0  -s 192.168.1.103/31      -j MARK --set-mark 0x40040001 >/dev/null 2>&1
iptables -A POSTROUTING -t mangle -o eth0  -s 192.168.1.103/31      -j MARK --set-mark 0x40040001
iptables -D POSTROUTING -t mangle -o br0  -d 192.168.1.104      -j MARK --set-mark 0x80040001 >/dev/null 2>&1
iptables -A POSTROUTING -t mangle -o br0  -d 192.168.1.104      -j MARK --set-mark 0x80040001
iptables -D POSTROUTING -t mangle -o eth0  -s 192.168.1.104      -j MARK --set-mark 0x40040001 >/dev/null 2>&1
iptables -A POSTROUTING -t mangle -o eth0  -s 192.168.1.104      -j MARK --set-mark 0x40040001
appdb rules: <000000>6<00006B>6<0D0007>5<0D0086>5<0D00A0>5<12003F>4<00001B>4<05****>4<06****>4<13****>4<14****>4<1A****>6
realtc filter change dev br0 prio 2 protocol all handle 827::800 u32 flowid 1:15
realtc filter change dev eth0 prio 2 protocol all handle 827::800 u32 flowid 1:15
realtc filter add dev br0 protocol all prio 2 u32 match mark 0x8000006B 0xc03fffff flowid 1:15
realtc filter add dev eth0 protocol all prio 2 u32 match mark 0x4000006B 0xc03fffff flowid 1:15
realtc filter add dev br0 protocol all prio 15 u32 match mark 0x800D0007 0xc03fffff flowid 1:14
realtc filter add dev eth0 protocol all prio 15 u32 match mark 0x400D0007 0xc03fffff flowid 1:14
realtc filter add dev br0 protocol all prio 15 u32 match mark 0x800D0086 0xc03fffff flowid 1:14
realtc filter add dev eth0 protocol all prio 15 u32 match mark 0x400D0086 0xc03fffff flowid 1:14
realtc filter add dev br0 protocol all prio 15 u32 match mark 0x800D00A0 0xc03fffff flowid 1:14
realtc filter add dev eth0 protocol all prio 15 u32 match mark 0x400D00A0 0xc03fffff flowid 1:14
realtc filter add dev br0 protocol all prio 20 u32 match mark 0x8012003F 0xc03fffff flowid 1:13
realtc filter add dev eth0 protocol all prio 20 u32 match mark 0x4012003F 0xc03fffff flowid 1:13
realtc filter add dev br0 protocol all prio 2 u32 match mark 0x8000001B 0xc03fffff flowid 1:13
realtc filter add dev eth0 protocol all prio 2 u32 match mark 0x4000001B 0xc03fffff flowid 1:13
realtc filter change dev br0 prio 8 protocol all handle 806::800 u32 flowid 1:13
realtc filter change dev eth0 prio 8 protocol all handle 806::800 u32 flowid 1:13
realtc filter change dev br0 prio 9 protocol all handle 807::800 u32 flowid 1:13
realtc filter change dev eth0 prio 9 protocol all handle 807::800 u32 flowid 1:13
realtc filter change dev br0 prio 22 protocol all handle 802::800 u32 flowid 1:13
realtc filter change dev eth0 prio 22 protocol all handle 802::800 u32 flowid 1:13
realtc filter change dev br0 prio 23 protocol all handle 804::800 u32 flowid 1:13
realtc filter change dev eth0 prio 23 protocol all handle 804::800 u32 flowid 1:13
realtc filter change dev br0 prio 2 protocol all handle 827::803 u32 flowid 1:15
realtc filter change dev eth0 prio 2 protocol all handle 827::803 u32 flowid 1:15
 

Attachments

  • 1.PNG
    1.PNG
    154.8 KB · Views: 117
  • 2.PNG
    2.PNG
    298.9 KB · Views: 119
  • 3.PNG
    3.PNG
    279.5 KB · Views: 114
  • 4.PNG
    4.PNG
    102.2 KB · Views: 116
  • 5.PNG
    5.PNG
    56.5 KB · Views: 123
I have a strange problem. My routed all traffic via iptables to/from my Aruba (enterprise VPN router) to the Work-from-Home category (screenshot 1) then in AppDB redirected email services and VOIP services (05**** & 06****) to Web Surfing (screenshot 2, to try to keep my Aruba traffic as isolated and high priority as possible).
So you redirect certain traffic (which happens to be unmarked as 000000) to a new category (060001), and also redirect that 06 category to a new class (Web Surfing).
In the tracked connections it indicates the Aruba (192.168.1.101)(screenshot 3) IS being put into the Work-from-Home group BUT in the pie chart (screenshot 4) it seems to indicate it is going to the Web Surfing group NOT Work-from-Home.
This is accurate because of the AppDB redirection for 06**** and a bug on my part to not consider AppDB wildcard rules after the iptables rules in this scenario. It's only an issue because the script chooses to use 060001 to represent the Work-From-Home/VoIP class, which can then be redirected based on the appdb rules (wildcard 06**** or an exact match on 060001). I think you can work around this for now by adding an AppDB rule to put 060001 (Skype) back into Work-From-Home (the coloring will still be incorrect but it will end up in the bucket you want). Or use the underused Game Downloads category for Aruba traffic and move it up to the top priority (called Learn-From-Home in the ASUS customize screen).
Then to throw one last curve ball at you I look at the Merlin classification page and it shows the Aruba (192.168.1.101) in the File Transferring category (screenshot 5). What am I missing here?
This is because Merlin took ASUS at their word and assumes that category priority 4 is the default category priority for Unmarked/Untracked traffic. My experience says Untracked traffic goes into whatever priority Work-From-Home is assigned (where category 00 Instant Messengers lives).

EDIT: I realize now that recommending the Game Downloads category at the top goes against my primary recommendation to leave Learn-From-Home at the bottom of the list due to its duplication of category 4. So I struck out that sentence above.

EDIT2: clarified priority/category terminology.
 
Last edited:
@Vexira Does your Flexqos classification work with the latest 384.19 beta?
Good question I just re installed form scratch because of the update and I'm getting the same issue as you on classification and flex with pps I just checked it.
That sounds out of my hands, but check if these commands return any output showing activity:
Code:
tc -s class show dev br0 | grep " parent 1:1 " -A2
tc -s class show dev eth0 | grep " parent 1:1 " -A2
 
Note-to-self and everyone smarter than me: I'm wondering if my rules evaluation would be simpler if I were to unshift the rules onto the array (i.e. in reverse order), instead of pushing them. Then I could go back to stopping after the first match of iptables rules, and then figure out if an AppDB rule overrides the new qos_class. And it should theoretically speed up the list processing.
 
That sounds out of my hands, but check if these commands return any output showing activity:
Code:
tc -s class show dev br0 | grep " parent 1:1 " -A2
tc -s class show dev eth0 | grep " parent 1:1 " -A2
ASUSWRT-Merlin RT-AX88U 384.19_alpha1-g9ca4b67bb0 Wed Jul 1 22:58:11 UTC 2020
@RT-AX88U-A868:/tmp/home/root# tc -s class show dev br0 | grep " parent 1:1 " -A2
class htb 1:11 parent 1:1 leaf 11: prio 1 rate 76032Kbit overhead 18 ceil 506880Kbit burst 126298b cburst 631319b
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
--
class htb 1:10 parent 1:1 leaf 10: prio 0 rate 25344Kbit overhead 18 ceil 506880Kbit burst 30371b cburst 631319b
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
--
class htb 1:13 parent 1:1 leaf 13: prio 3 rate 101376Kbit overhead 18 ceil 506880Kbit burst 30286b cburst 631319b
Sent 686 bytes 2 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
--
class htb 1:12 parent 1:1 leaf 12: prio 2 rate 152064Kbit overhead 18 ceil 506880Kbit burst 62232b cburst 631319b
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
--
class htb 1:15 parent 1:1 leaf 15: prio 5 rate 50688Kbit overhead 18 ceil 506880Kbit burst 17544b cburst 631319b
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
--
class htb 1:14 parent 1:1 leaf 14: prio 4 rate 25344Kbit overhead 18 ceil 506880Kbit burst 23965b cburst 631319b
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
--
class htb 1:17 parent 1:1 leaf 17: prio 7 rate 50688Kbit overhead 18 ceil 506880Kbit burst 4745b cburst 631319b
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
--
class htb 1:16 parent 1:1 leaf 16: prio 6 rate 25344Kbit overhead 18 ceil 506880Kbit burst 11167b cburst 631319b
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
ctva@RT-AX88U-A868:/tmp/home/root# tc -s class show dev eth0 | grep " parent 1:1 " -A2
class htb 1:11 parent 1:1 leaf 11: prio 1 rate 5990Kbit overhead 18 ceil 39936Kbit burst 9590b cburst 49540b
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
--
class htb 1:10 parent 1:1 leaf 10: prio 0 rate 1996Kbit overhead 18 ceil 39936Kbit burst 3194b cburst 49540b
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
--
class htb 1:13 parent 1:1 leaf 13: prio 3 rate 7987Kbit overhead 18 ceil 39936Kbit burst 3190b cburst 49540b
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
--
class htb 1:12 parent 1:1 leaf 12: prio 2 rate 3993Kbit overhead 18 ceil 39936Kbit burst 4794b cburst 49540b
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
--
class htb 1:15 parent 1:1 leaf 15: prio 5 rate 3993Kbit overhead 18 ceil 39936Kbit burst 3194b cburst 49540b
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
--
class htb 1:14 parent 1:1 leaf 14: prio 4 rate 1996Kbit overhead 18 ceil 39936Kbit burst 3194b cburst 49540b
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
--
class htb 1:17 parent 1:1 leaf 17: prio 7 rate 11980Kbit overhead 18 ceil 39936Kbit burst 3186b cburst 49540b
Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
--
class htb 1:16 parent 1:1 leaf 16: prio 6 rate 1996Kbit overhead 18 ceil 39936Kbit burst 3194b cburst 49540b
Sent 913148 bytes 11457 pkt (dropped 0, overlimits 0 requeues 0)
rate 0bit 0pps backlog 0b 0p requeues 0
ctva@RT-AX88U-A868:/tmp/home/root#
 
is FlexQoS broken for the 384.19A1? I saw all the post here and decided to uninstsall FlexQoS before upgrading to 384.19A1 and it seems fine. Not sure to install FlexQoS back on
 

Sign Up For SNBForums Daily Digest

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