FlexQoS FlexQoS 1.4.8 - Flexible QoS Enhancement Script for Adaptive QoS

[ExtremeFiretop]

Release Notes for FlexQoS 1.4.7 production release now available
[2025-June-15]

The fork from @dave14305 's repository is now hosted on the AMTM-OSR GitHub repo:

GitHub - AMTM-OSR/FlexQoS: FlexQoS - Flexible QoS Enhancement Script for Adaptive QoS on ASUSWRT-Merlin

FlexQoS - Flexible QoS Enhancement Script for Adaptive QoS on ASUSWRT-Merlin - AMTM-OSR/FlexQoS

github.com

1) Re-enable develop branch for script development.

2) Allow script to remain in failed update process as reported by @maghuro here: Improvement regarding update #1
-Previously the script would uninstall itself in a failed update.

3) Added warning for users installing on 3006 routers without functioning QoS in PR: Add Warning Messages for Adaptive QoS #8
-Warnings may take anywhere from 15 seconds to 3 minutes after install to display. Example screenshots below:

 

[dave14305]

3) Added warning for users installing on 3006 routers without functioning QoS

Based on the discussion in the 3006.102.5 beta thread, this should become a hard failure instead of a warning. It seems it is no longer safe to install FlexQoS on the newest GPL code.

In a laughable bit of irony, I can’t even fork the new OSR repository for a PR since I already have the original repo under my name. So someone else will need to give it a go. There is already a check for rc_support during installation, but a new negative check for wifi7 needs to be added.

Beta - Asuswrt-Merlin 3006.102.5 Beta is now available

Ah, a misunderstanding from the previous posts then. I created a post on how to tell if drivers have changed. Just because the date changes does not mean a newer driver you also have to look at the driver version number...

www.snbforums.com

 

[ExtremeFiretop]

Based on the discussion in the 3006.102.5 beta thread, this should become a hard failure instead of a warning. It seems it is no longer safe to install FlexQoS on the newest GPL code.

Thanks for bringing this to our attention Dave. It's always appreciated. We can turn it into a hard fail instead of a soft warning.

In a laughable bit of irony, I can’t even fork the new OSR repository for a PR since I already have the original repo under my name. So someone else will need to give it a go. There is already a check for rc_support during installation, but a new negative check for wifi7 needs to be added.

Beta - Asuswrt-Merlin 3006.102.5 Beta is now available

Ah, a misunderstanding from the previous posts then. I created a post on how to tell if drivers have changed. Just because the date changes does not mean a newer driver you also have to look at the driver version number...

www.snbforums.com

Haha that is funny.

You could technically just unarchive it? and then start submitting PRs to OSR that way if you so choose

 

[dave14305]

You could technically just unarchive it? and then start submitting PRs to OSR that way if you so choose

I still can’t fork the OSR repo, and adding branches to my original repo feels awkward since OSR is a fork of my repo. Seems it’s technically possible, but better to let the original lie dormant.

 

[ExtremeFiretop]

I still can’t fork the OSR repo, and adding branches to my original repo feels awkward since OSR is a fork of my repo. Seems it’s technically possible, but better to let the original lie dormant.

Understandable. We'll check into this news for FlexQoS later this evening.

 

[swejuggalo]

Thanks for bringing this to our attention Dave. It's always appreciated. We can turn it into a hard fail instead of a soft warning.



Haha that is funny.

You could technically just unarchive it? and then start submitting PRs to OSR that way if you so choose

Yeah, I tried and failed drastically to have FlexQoS on my router. Twice, first at the beta update, and then replicated it and found out that FlexQoS was the reason of failure. I was practically just holding on to it just in case a fix would ever come.
I have no way to fetch any suitable logs (that I know of) to point into the right direction of why it fails so terrible now, but could install on previous firmware without drastic failures (other than its own failure).
As it looks now, BE-routers and functional FlexQoS might never happen anyway. So better block attempts to install it.

 

[ExtremeFiretop]

Release Notes for FlexQoS 1.4.8 production release now available
[2025-July-10]

The fork from @dave14305 's repository is now hosted on the AMTM-OSR GitHub repo:

GitHub - AMTM-OSR/FlexQoS: FlexQoS - Flexible QoS Enhancement Script for Adaptive QoS on ASUSWRT-Merlin

FlexQoS - Flexible QoS Enhancement Script for Adaptive QoS on ASUSWRT-Merlin - AMTM-OSR/FlexQoS

github.com

What's changed/new?

v1.4.8 (18-May-2025)
- CHANGED: Changed the soft warning for hard block on WiFi 7 devices as per dave and RMerlin conversation here: https://www.snbforums.com/threads/asuswrt-merlin-3006-102-5-beta-is-now-available.95115/post-961105

- CHANGED: Added a force uninstall for routers with FlexQoS installed on BE devices while rebooting/startup

 

[ExtremeFiretop]

Yeah, I tried and failed drastically to have FlexQoS on my router. Twice, first at the beta update, and then replicated it and found out that FlexQoS was the reason of failure. I was practically just holding on to it just in case a fix would ever come.
I have no way to fetch any suitable logs (that I know of) to point into the right direction of why it fails so terrible now, but could install on previous firmware without drastic failures (other than its own failure).
As it looks now, BE-routers and functional FlexQoS might never happen anyway. So better block attempts to install it.

Thanks @swejuggalo for reporting. A hard block has now been implemented for WiFi 7 devices.
Only WiFi 6E or below will be allowed to use FlexQoS moving forwards.

 

[swejuggalo]

Release Notes for FlexQoS 1.4.8 production release now available
[2025-July-10]

The fork from @dave14305 's repository is now hosted on the AMTM-OSR GitHub repo:

GitHub - AMTM-OSR/FlexQoS: FlexQoS - Flexible QoS Enhancement Script for Adaptive QoS on ASUSWRT-Merlin

FlexQoS - Flexible QoS Enhancement Script for Adaptive QoS on ASUSWRT-Merlin - AMTM-OSR/FlexQoS

github.com

What's changed/new?

v1.4.8 (18-May-2025)
- CHANGED: Changed the soft warning for hard block on WiFi 7 devices as per dave and RMerlin conversation here: https://www.snbforums.com/threads/asuswrt-merlin-3006-102-5-beta-is-now-available.95115/post-961105
View attachment 66615

- CHANGED: Added a force uninstall for routers with FlexQoS installed on 3004 F/W while upgrading to 3006 F/W
View attachment 66616

Hurrah! No more break downs

 

[dave14305]

Summary of FlexQoS usefulness:
WiFi5 (ac) - rock solid
WiFi6 (ax) - so-so if you can live without either iptables rules or flow cache (hw acceleration), less than 400 Mbit ISP service.
WiFi7 (be) - crashes your router on the latest firmware

 

[ExtremeFiretop]

Summary of FlexQoS usefulness:
WiFi5 (ac) - rock solid
WiFi6 (ax) - so-so if you can live without either iptables rules or flow cache (hw acceleration), less than 400 Mbit ISP service.
WiFi7 (be) - crashes your router on the latest firmware

I'm curious to see what ASUS plans for QoS replacement in WiFi 7 (be) devices.

 

[swejuggalo]

Never really used it when it was in it's "glory days" (when I used a AC router).
It's was more a fun experiment to even take a look at it.
Glad I crashed so others would not

 

[dave14305]

As the demise draws nearer, it is a fun trip down memory lane to revisit the origins of the original custom QoS script that started it all. I only took over in 2020 after FreshJR disappeared or died.

[Release] FreshJR Adaptive QOS (Improvements / Custom Rules / and Inner workings)

Welcome to FreshJR's Adaptive QOS modification script! Issues with Adaptive QoS: Adaptive QOS works amazing, but I have decided to tweak it as I have a few issues with its performance out of the box. Some of the issues are as follows: Issue 1: The first issue is caused by the traffic groups...

www.snbforums.com

 

[dave14305]

I'm curious to see what ASUS plans for QoS replacement in WiFi 7 (be) devices.

The QoS problem is largely solved on other platforms like OpenWrt. They have solutions for general use, gaming, classifying traffic up the wazoo, whatever you like. Classify it on egress and it can automatically classify the return ingress traffic the same way. Gamers get better “ping” from the HFSC qdisc than CAKE.

Hopefully they are following a similar path, and I see hints in the source that suggests the ingress issue is being developed, but I really don’t know their plans. Dumping Trend Micro would be a good start.