378.50 Bug ? Adaptive QOS - being affected by traditional QoS settings.

[NGRhodes]

Last night I found a reproducible issue on my AC56U

When I enable traditional QoS and make changes to either the priorities or rules (ive not narrowed down to exactly which yet), and then switch [back] to Adaptive QoS it appears not to activate Adaptive QoS and all traffic gets classified as general.
I did 3 factory wipes to check and each time adaptive QoS worked until I fiddled with traditional QoS settings and then would not work again until factory reset.

it looks like the device priorities are stored in the traditional rules as you can see your device priorities on the Bandwidth monitor screen on the traditional QoS rules screen.

Would be nice if someone else could try reproducing/confirming.

Cheers, Nick

 

[NGRhodes]

Looking at the source confirms what I said about device priorities being stored in the traditional ruleset.

Another interesting thing I spotted in the watchdog.c is that the signatures used by Adaptive QoS are updated on every boot OR 2 days

Digging round the tmp files this looks like the default device priorities:

{0, 40%, 100%, 40%, 100%}
{1, 30%, 100%, 30%, 100%}
mac=????????????
{2, 20%, 100%, 20%, 100%}
mac=????????????
mac=????????????
{3, 15%, 100%, 15%, 100%}
cat=na
{4,  5%, 100%,  5%, 100%}
mac=????????????

I've blanked my macs out, but it looks like the default category is 3, which is LOW.

 

[chris.at]

You are right with the default-category "LOW", even for traditional QOS it's "LOW".

It would be really nice if this could be changed to "LOWEST" or even better implement a dropdown to select the default priority by your needs.