FlexQoS FlexQoS - Flexible QoS Enhancement Script for Adaptive QoS

  • ATTENTION! You'll notice a Prefix dropdown when you create a thread. If your post applies to one of the topics listed, please use that Prefix for your post. When browsing the thread list you can use the Prefix to filter the view.
  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

dave14305

Part of the Furniture
Updated to 0.5 beta:
- Fixed setting defaults on clean installs
- Fixed UI loading when FreshJR was not installed
Code:
flexqos -update
# or
sh /jffs/addons/flexqos/flexqos.sh -update
 
Last edited:

Vexira

Part of the Furniture
Updated to 0.5 beta:
- Fixed setting defaults on clean installs
- Fixed UI loading when FreshJR was not installed
Thank you sooo much, also does that fix that rate error I'm getting after it applies custom rules, I'm still getting them even though I did the re install with the fresh jr install first.
 

dave14305

Part of the Furniture
so is felxqos even in the beta better than the reguald freshjr script ?, does it also work well with steam and cs go implements ?
are there any options to add 95% rule /hardcoded?
It's a major re-write, so it's possibly less stable than the develop version I had posted in the FreshJR thread, but all my focus will be on this new version. You can wait a little while in case more bugs are found by other volunteers. :)

I don't do any gaming, so I don't think it would help or hurt more than the original script.

I don't really like the idea of hardcoding values in the script, since bandwidth is a very sensitive issue. 95% is probably a minimum guideline, but some might require 85% or 90%...
 

dave14305

Part of the Furniture
Thank you sooo much, also does that fix that rate error I'm getting after it applies custom rules, I'm still getting them even though I did the re install with the fresh jr install first.
That is the intention. Fingers crossed!
 

Vexira

Part of the Furniture
That is the intention. Fingers crossed!
Ok sweet I'll let you know how it goes, I'll have to run the update and check, question aslo if I added the hard coded 95% rule will the update remove it?
 

Smokey613

Senior Member
Okay, I installed FlexQoS and now my sys log is flooded with:


Jun 25 09:14:28 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:28 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:28 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:28 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: net_ratelimit: 887 callbacks suppressed
Jun 25 09:14:32 RT-AC86U kernel: protocol 0000 is buggy, dev eth0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: net_ratelimit: 943 callbacks suppressed
Jun 25 09:14:38 RT-AC86U kernel: protocol 0000 is buggy, dev eth0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
 

dave14305

Part of the Furniture
Ok sweet I'll let you know how it goes, I'll have to run the update and check, question aslo if I added the hard coded 95% rule will the update remove it?
Yes, it overwrites the script with impunity.
 

dave14305

Part of the Furniture
app DB doesn't support wildcard rules. When I entered 14**** it throws a red box (meaning that it is wrong, which it isn't because the hard coded rules mostly have wildcards)
I can't reproduce this. Can you take a screenshot when it happens again? Make sure there are no spaces at the beginning or end, and that you have 4 asterisks ****
 

QuikSilver

Very Senior Member
Updated to 0.5 beta:
- Fixed setting defaults on clean installs
- Fixed UI loading when FreshJR was not installed
@dave14305 , you may want to edit your first post on how users can update their current version to the latest without having to search for it. Just a thought....
 

dave14305

Part of the Furniture
Okay, I installed FlexQoS and now my sys log is flooded with:


Jun 25 09:14:28 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:28 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:28 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:28 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: net_ratelimit: 887 callbacks suppressed
Jun 25 09:14:32 RT-AC86U kernel: protocol 0000 is buggy, dev eth0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: net_ratelimit: 943 callbacks suppressed
Jun 25 09:14:38 RT-AC86U kernel: protocol 0000 is buggy, dev eth0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
I don't know what could cause that, especially since I don't have an 86U or other HND router. There's nothing extra fancy about the resulting iptables or tc rules compared to the previous versions, so maybe a reboot will help clear things up.
 

QuikSilver

Very Senior Member
Okay, I installed FlexQoS and now my sys log is flooded with:


Jun 25 09:14:28 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:28 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:28 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:28 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: net_ratelimit: 887 callbacks suppressed
Jun 25 09:14:32 RT-AC86U kernel: protocol 0000 is buggy, dev eth0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:32 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: net_ratelimit: 943 callbacks suppressed
Jun 25 09:14:38 RT-AC86U kernel: protocol 0000 is buggy, dev eth0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
Jun 25 09:14:38 RT-AC86U kernel: protocol 86dd is buggy, dev br0
This doesn't look related to this script. Searching I found this person with similar message.
I'm using an ASUS RT-AC86U router and the latest firmware version (384.10). This issue is not related to this firmware version, it's been happening since a long time, even on my previous RT-AC68U if I recall correctly.

My WAN connection is through DHCP, since I have a Peplink Balance One router doing Load Balancing. Whenever I enable IPv6 in passthrough mode, I get loads and loads of these messages on the system log:

Mar 26 09:21:23 kernel: net_ratelimit: 27 callbacks suppressed
Mar 26 09:21:30 kernel: net_ratelimit: 2 callbacks suppressed
Mar 26 09:21:35 kernel: net_ratelimit: 16 callbacks suppressed
Mar 26 09:21:43 kernel: net_ratelimit: 437 callbacks suppressed
Mar 26 09:21:48 kernel: net_ratelimit: 3508 callbacks suppressed
Mar 26 09:21:53 kernel: net_ratelimit: 1 callbacks suppressed
Mar 26 09:21:59 kernel: net_ratelimit: 24669 callbacks suppressed
Mar 26 09:22:04 kernel: net_ratelimit: 58701 callbacks suppressed
Mar 26 09:22:10 kernel: net_ratelimit: 737 callbacks suppressed
Mar 26 09:22:16 kernel: net_ratelimit: 15 callbacks suppressed
Mar 26 09:22:22 kernel: net_ratelimit: 28 callbacks suppressed
Mar 26 09:22:29 kernel: net_ratelimit: 5 callbacks suppressed
Mar 26 09:22:35 kernel: net_ratelimit: 174 callbacks suppressed
Mar 26 09:22:40 kernel: net_ratelimit: 1029 callbacks suppressed
Mar 26 09:22:46 kernel: net_ratelimit: 14 callbacks suppressed
Mar 26 09:22:51 kernel: net_ratelimit: 15 callbacks suppressed
Mar 26 09:22:56 kernel: net_ratelimit: 9 callbacks suppressed
Mar 26 09:23:01 kernel: net_ratelimit: 44217 callbacks suppressed
Mar 26 09:23:06 kernel: net_ratelimit: 104175 callbacks suppressed
Mar 26 09:23:12 kernel: net_ratelimit: 34246 callbacks suppressed
Mar 26 09:23:17 kernel: net_ratelimit: 49 callbacks suppressed
Mar 26 09:23:22 kernel: net_ratelimit: 145 callbacks suppressed
Mar 26 09:23:27 kernel: net_ratelimit: 1200 callbacks suppressed
Mar 26 09:23:33 kernel: net_ratelimit: 59 callbacks suppressed
Mar 26 09:23:41 kernel: net_ratelimit: 16 callbacks suppressed

If I connect through SSH and run dmesg, I get messages like these:

protocol 86dd is buggy, dev br0
net_ratelimit: 69 callbacks suppressed
protocol 0800 is buggy, dev eth0
protocol 0800 is buggy, dev br0
protocol 0800 is buggy, dev br0
protocol 0800 is buggy, dev eth0
protocol 0800 is buggy, dev eth0
protocol 0800 is buggy, dev br0
protocol 0800 is buggy, dev eth0
protocol 86dd is buggy, dev eth0
protocol 86dd is buggy, dev br0
protocol 86dd is buggy, dev br0
net_ratelimit: 1105 callbacks suppressed
protocol 0800 is buggy, dev eth0
protocol 0800 is buggy, dev br0
protocol 0800 is buggy, dev eth0
protocol 0800 is buggy, dev eth0
protocol 0800 is buggy, dev br0
protocol 0800 is buggy, dev br0
protocol 0800 is buggy, dev eth0
protocol 0800 is buggy, dev eth0
protocol 86dd is buggy, dev eth0
protocol 0800 is buggy, dev br0

I understand that 0800 is the EtherType for IPv4 and that 86dd is the EtherType for IPv6. But I can't figure out how to solve these error messages.

Besides that, both IPv4 and IPv6 connections work just fine.

Any ideas?
https://www.snbforums.com/threads/protocol-0800-is-buggy-protocol-86dd-is-buggy.55762/

Edit: Found here as well.
https://www.snbforums.com/threads/q...86u-kernel-protocol-0800-is-buggy-spam.61063/
 

Spydawg

Regular Contributor
would I see any improvements with this on a fiber 1.5g up/down connection?
 

Smokey613

Senior Member

Therion87

Regular Contributor
would I see any improvements with this on a fiber 1.5g up/down connection?
No. An AC3100 can't even support that connection without QoS.
 

QuikSilver

Very Senior Member
would I see any improvements with this on a fiber 1.5g up/down connection?
Why kind of improvements are you expecting? I wouldn't think you would with those kinds of speeds. Most have lower speeds and want items like VOIP and video to be a higher priority than a file download or gaming. With your speeds I wouldn't think those items would get maxed out or bottlenecked.
 

QuikSilver

Very Senior Member
You are correct.... it was just a coincidence that I only observed the errors after installing FlexQos. I will disable the IPv6 then.
That is interesting. I don't use IPv6 but do share the same model as you. Might be why my log doesn't show them.
 

mbze430

Regular Contributor
You are correct.... it was just a coincidence that I only observed the errors after installing FlexQos. I will disable the IPv6 then.
It might be a router firmware issue? because I am on a AX88U using IPv6 with the script and I don't see those errors
 

ugandy

Senior Member
You are correct.... it was just a coincidence that I only observed the errors after installing FlexQos. I will disable the IPv6 then.
if you also have suricata running while using qos, you will see these messages. i did.
 

Jgee

Occasional Visitor
Can anyone confirm this actually works on the ax58u? As far as limiting upload and download speeds properly to combat bufferbloat? Be a lot of work to change everything back over to merlin, just to find out still doesn't work.
 

Smokey613

Senior Member
It might be a router firmware issue? because I am on a AX88U using IPv6 with the script and I don't see those errors
It appears to be related to using IPv6 in Passthrough mode and any type of Qos. I am unable to use Native mode due my ISPs setup on IPv6.
 

Similar threads

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