FlexQoS FlexQoS 1.5.1 - Flexible QoS Enhancement Script for Adaptive QoS

[irfan44]

Update:
Until 3006.102.4 & betas I always did a reset and tried but Flexqos never worked and result was intermittent freezes and Internet failures.

On 3006.102.5 I did a dirty upgrade and flexqos still did the same so I didn't bother to reset the router (AX88U Pro) & uninstalled Flexqos.

@ExtremeFiretop and @Kingp1n suggested to remove IP Table rules which worked.
So I did a WPS reset and installed flexqos. But WPS reset didn't clear everything and I had difficulty doing SSH and accessing router GUI.
So I again did a complete reset from within the GUI and installed flexqos again. Now it's been more than 24 hours and everything is working flawless (no I did not remove any default rules).
I think it's safe to assume that Flexqos is still OK for AX routers.
Will let you all know if I run into any problems later

 

[ExtremeFiretop]

I won't take any credit for @dave14305 's idea. I'm not sure what would of caused that issue/conflict exactly, but I'm happy it appears to be working after the reset!

 

[ExtremeFiretop]

As someone once said: no news is good news.
I've been trying to catch something to talk about but hey, I haven't found anything
Everything is working smoothly with my two schedules , one for weekdays and the other one for weekends.

The only picky thing I have is when I want to change one particular schedule, I have to configure them from scratch. But that will happen once in a year, so that's not even a issue.

Everything is smooth!

Thanks once again for your work

Hi @maghuro

Based on your feedback; I've made some more changes in my PR and finally merged it into dev branch.
At this point I would call it "beta" testing instead of "alpha" testing

You can run the following to get the latest develop version:

sh /jffs/addons/flexqos/flexqos.sh develop

Below are some sample screenshots of the implementation thus far...
Please test some more to confirm this addresses all your requirements and doesn't have any unforeseen bugs I didn't catch.

-SSH

-WebUI:

 

[maghuro]

Hi @maghuro

Based on your feedback; I've made some more changes in my PR and finally merged it into dev branch.
At this point I would call it "beta" testing instead of "alpha" testing

You can run the following to get the latest develop version:

sh /jffs/addons/flexqos/flexqos.sh develop

Below are some sample screenshots of the implementation thus far...
Please test some more to confirm this addresses all your requirements and doesn't have any unforeseen bugs I didn't catch.

-SSH
View attachment 67584

-WebUI:
View attachment 67585

Thank you, very nice work!

One thing I noticed already is when I set something to some value between two hours, it only assumes the hour and sets the minutes to zero.
For example, I set a cron to start as 07:45 and it was set to start at 7h.

On the GUI, it assumes 07:45 as you can see, but the cron stays at 7.

================ QoS Schedule =================
Saved schedule records:
  1) [ON] DOW=1-5  06:45 -> 00:00
  2) [ON] DOW=0,6  09:00 -> 02:00
Active cron entries (if any):
  0 6 * * 1-5 /jffs/addons/flexqos/flexqos.sh -qosstart #flexqos_qoson_1#
  0 0 * * 1-5 /jffs/addons/flexqos/flexqos.sh -qosstop #flexqos_qosoff_2#
  0 9 * * 0,6 /jffs/addons/flexqos/flexqos.sh -qosstart #flexqos_qoson_3#
  0 2 * * 0,6 /jffs/addons/flexqos/flexqos.sh -qosstop #flexqos_qosoff_4#
Choose an option:
  1) Create schedules (Guided)
  2) Add a schedule
  3) Edit a schedule
  4) Delete a schedule
  5) Clear ALL schedules
  e) Exit
-----------------------------------------------
Enter selection: 3
  1) [ON] DOW=1-5  06:45 -> 00:00
  2) [ON] DOW=0,6  09:00 -> 02:00
Pick schedule # (1-2, or e=exit): 1
Editing schedule #1
Enable? (1=yes,0=no) [1]: 1
Days of week (e.g., *,1-5,0,6) [1-5]: 1-5
START time (HH or HH:MM) [06:45]: 07:45
END time (HH or HH:MM) [00:00]: 00:00
Updated and applied.
================ QoS Schedule =================
Saved schedule records:
  1) [ON] DOW=1-5  07:45 -> 00:00
  2) [ON] DOW=0,6  09:00 -> 02:00
Active cron entries (if any):
  0 7 * * 1-5 /jffs/addons/flexqos/flexqos.sh -qosstart #flexqos_qoson_1#
  0 0 * * 1-5 /jffs/addons/flexqos/flexqos.sh -qosstop #flexqos_qosoff_2#
  0 9 * * 0,6 /jffs/addons/flexqos/flexqos.sh -qosstart #flexqos_qoson_3#
  0 2 * * 0,6 /jffs/addons/flexqos/flexqos.sh -qosstop #flexqos_qosoff_4#
Choose an option:
  1) Create schedules (Guided)
  2) Add a schedule
  3) Edit a schedule
  4) Delete a schedule
  5) Clear ALL schedules
  e) Exit

Edit: however, I tried to set this schedule through webui and it was set correctly (after that, I checked via ssh and it was correct)

 

[ExtremeFiretop]

Thank you, very nice work!

One thing I noticed already is when I set something to some value between two hours, it only assumes the hour and sets the minutes to zero.
For example, I set a cron to start as 07:45 and it was set to start at 7h.

On the GUI, it assumes 07:45 as you can see, but the cron stays at 7.



Edit: however, I tried to set this schedule through webui and it was set correctly (after that, I checked via ssh and it was correct)

Great catch! @maghuro ! This should now be addressed
I was actually more focused on the WebUI recently; so it's clear to me I missed this originally.

Was a bit of an oversight on my original flow I had planned in my head; I actually was only considering hours and dropping the minutes over SSH.
Re-downloading the latest develop version should solve this report. Let me know!

 

[saison2023]

Spoiler: Hi [USER=67697

@maghuro[/USER]

Based on your feedback; I've made some more changes in my PR and finally merged it into dev branch.
At this point I would call it "beta" testing instead of "alpha" testing

You can run the following to get the latest develop version:

sh /jffs/addons/flexqos/flexqos.sh develop

Below are some sample screenshots of the implementation thus far...
Please test some more to confirm this addresses all your requirements and doesn't have any unforeseen bugs I didn't catch.

-SSH
View attachment 67584

-WebUI:
View attachment 67585

This looks like very promising/interesting.
I will surely have a look later because I really like the idea of scheduling QoS.
Thank you very much for the hard work and for people that are proposing brilliant idea that can be useful for others.

 

[maghuro]

Great catch! @maghuro ! This should now be addressed
I was actually more focused on the WebUI recently; so it's clear to me I missed this originally.

Was a bit of an oversight on my original flow I had planned in my head; I actually was only considering hours and dropping the minutes in SSH.
Re-downloading the latest develop version should solve this report. Let me know!

Perfect! Nothing to declare !

GREAT job. I was checking your code and it's a brilliant implementation

 

[Kingp1n]

Hi @maghuro

Based on your feedback; I've made some more changes in my PR and finally merged it into dev branch.
At this point I would call it "beta" testing instead of "alpha" testing

You can run the following to get the latest develop version:

sh /jffs/addons/flexqos/flexqos.sh develop

Seems all is working well with "beta" testing for qos scheduling. Cool feature. Hope youre able to realase as stable soon.

I appreciate the continued support for FlexQoS!!

 

[ExtremeFiretop]

Seems all is working well with "beta" testing for qos scheduling. Cool feature. Hope youre able to realase as stable soon.

I appreciate the continued support for FlexQoS!!

I noticed an "issue" with the scheduling UI on some browsers specifically, while most are fine the spacing for others is a bit off.

so I'm currently pondering the best way to handle it.

 

[maghuro]

Situation:
All traffic (only ipv4, I don't use ipv6) from a specific machine is manually redirected to the Work-from-Home rule (yellow). It correctly shows on the table (screenshot1)
However, on the graphic, it isn't applied. I run a test from fast.com (netflix speedtest), and all the traffic, on the graphic, shows on Video/Audio streaming (green) category (and net control packets? ). (screenshot2 during a fast.com test)

My rules are on screenshot3.

I'll send you via pm the debug from flexqos.

Thanks in advance!

 

[dave14305]

All traffic (only ipv4, I don't use ipv6) from a specific machine is manually redirected to the Work-from-Home rule (yellow). It correctly shows on the table (screenshot1)
However, on the graphic, it isn't applied. I run a test from fast.com (netflix speedtest), and all the traffic, on the graphic, shows on Video/Audio streaming (green) category (and net control packets? ). (screenshot2 during a fast.com test)

That’s normal for iptables rules to be ignored on the latest models due to flow cache. It’s been discussed for a couple years already.

 

[ExtremeFiretop]

Release Notes for FlexQoS 1.4.9 production release now available
[2025-Sep-05]

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.9 (05-Sep-2025)
- NEW: Includes Flexible/Dynamic Scheduling of the QoS system on ASUS routers.
- As requested here by @maghuro : https://www.snbforums.com/threads/f...ent-script-for-adaptive-qos.94976/post-964632
- NOTE ON BROWSER LIMITATIONS:
Currently all web browsers have a "Time Picker" Widget except for Firefox.
This means that all browser's should have something like this available:

Even mobile browsers show like this:

However Firefox does not and instead only allows text input as found below:

This is not a bug with the code, but a limitation within Firefox.

Screenshots below:
-WebUI:

-SSH

 

[maghuro]

Well I don't know how I missed it, but...
The new scheduling option should be present in the settings backup...

 

[ExtremeFiretop]

Well I don't know how I missed it, but...
The new scheduling option should be present in the settings backup...

Good Morning @maghuro

You are absolutely right, working on this now!
I also noticed I didn't do a very good job cleaning up the cron jobs in an uninstall, which will be included in the next release.

 

[ExtremeFiretop]

Release Notes for FlexQoS 1.4.10 production release now available
[2025-Sep-06]

What's changed/new?

v1.4.10 (06-Sep-2025)
- FIXED: Addressed missing cleanup for any cron job schedules when uninstalling.
- FIXED: Missing the ability to backup the new QoS schedules as reported by @maghuro

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

 

[Kingp1n]

Release Notes for FlexQoS 1.4.10 production release now available
[2025-Sep-06]

What's changed/new?

v1.4.10 (06-Sep-2025)
- FIXED: Addressed missing cleanup for any cron job schedules when uninstalling.
- FIXED: Missing the ability to backup the new QoS schedules.

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

I tried updating and i'm getting this:

 

[ExtremeFiretop]

I tried updating and i'm getting this:

Thanks for reporting, seems to me that there's some kinda check in the script blocks version like 1.4.(10)
I guess the expectation was to go to 1.5.0 even though it's a small patch.

I can either update the code to stop caring, or update the version to be within the expected range.
Considering that your stuck with the old code now, I think I'll do both to be sure this is not a problem in the future.

One momento

 

[ExtremeFiretop]

I tried updating and i'm getting this:

Sorry again @Kingp1n
I've fixed it now as seen below:

 

[ExtremeFiretop]

Release Notes for FlexQoS 1.5.0 production release now available
[2025-Sep-06]

What's changed/new?

v1.5.0 (06-Sep-2025)
- FIXED: Allow script versions with double-digit segments by @Kingp1n

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

 

[Kingp1n]

Release Notes for FlexQoS 1.5.0 production release now available
[2025-Sep-06]

What's changed/new?

v1.5.0 (06-Sep-2025)
- FIXED: Allow script versions with double-digit segments.

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

Updated smoothly...

Only thing I noticed is when qos is scheduled it does turn off qos successfully however when I check Flow Cache under System info its showing as disabled. I do use iptable rules and i have Flow Cache Control set to Auto.

I believe this is how FC control works:

Post in thread 'ax88u-pro: need adaptive qos advice for 5 adults on a 300/300 isp' https://www.snbforums.com/threads/a...r-5-adults-on-a-300-300-isp.95307/post-965702

Normally when qos is disabled FC should be Enabled (default).