I am curious if anyone can comment, I am trying to do a test configuration with QoS in bandwidth manager (latest current ClearOS Community Edition). I have referred to the docs setup hints at the URL, https://www.clearos.com/resources/documentation/clearos/content:en_us:6_qos as a starting point.

I setup a number of different priority classes, as per the example at the URL above, and designated amounts of guaranteed bandwidth for these traffic types.
-- DNS gets highest priority,
-- Voip gets high priority,
-- http and https get a somewhat lower priority,

What I'm curious about is-- the behaviour of 'everything else' in these circumstances. For instance "traffic that does not match any of the rules" - will it default into the higest priority queue? The lowest priority queue? I tested and created a rule that matched "Everything" and forced to 'lowest priority'. And I can't see any difference in how things work. But my testing is not with a lot of systems/devices, so it is really not a 'valid test'. (just a small pre-deploy testing environment).

Ideally I would like 'all traffic by default' to go into the 'lowest' priority queue and then only designated (traffic for which specific rules exist) to be matched and get into the higher priority queues. But I'm not sure this is how the tool works; if I need to create a 'catch all' rule and then assume 'specific rules match first, catch all matches last' or if my 'catch all' rule is in fact just making a mess of things / since it will do this 'properly and automatically already'.

I did find another article in ClearOS documentation on the topic, but it is older (2013) and I'm not entirely clear it is about the 'same implementation of bandiwdth manager/QoS features'. And it also does not specifically talk about the topic I am curious about, ie, what is the behaviour of 'default' traffic. That URL/document was: https://www.clearos.com/resources/documentation/clearos/content:en_us:dev_apps_taking_qos_for_a_spin for reference.

Anyhow. If anyone has used QoS features, and is willing to give me a quick pointer about what the 'expected behaviour' is around 'all traffic not matching' in terms of what QoS priority queue (1-7) it will be assigned into, that would be greatly appreciated. Or any general comments on how well it works / what configs are known to work well / what configs are known to work poorly (or configs to avoid ..)

(* Context - Broadly speaking I am hoping to use in an environment for a non-profit, where they have 'highly variable' demands on their network - most of the time things are 'easy' and there are few people on the network; but occasionally they host an event / presentation / etc; have lots of devices on the LAN for a few hours - maybe 200-ish people/devices -- and at these times, I need something which will put some controls on how bandwidth is being doled out to people - ideally I want DNS, then VOip, then legitimate-regular web traffic to be priority - in that order - and then 'all other traffic' I want to be pushed into 'lower level queue' so that - at least those core things - DNS/Voip/Web - will work 'reasonably well as possible' / and that other unrecognized/undesignated traffic will be less likely to compete effectively for bandwidth against those 'preferred priority traffic types' during the ~intermittent times of ~higher activity on the network. Right now I have them setup with an "Edgerouter" entry level unit, and it appears to not have enough CPU power to utilize the ISP bandwidth fully when QoS/traffic controls are in place, so I'm hoping I can use ClearOS to improve the use of ISP Pipe / while still using QoS features to provide a 'decent internet access' level-of-service at the site). (Arguably maybe a 'big edgerouter' would fix the problem, but there is no budget to buy such a thing).

Many thanks for the help!

Tim