I understand that in the QOS section more specific rules need to be towards the top and more general rules towards the bottom when there's overlap between the rules since the first rule that matches is the one that gets used.
But I have a situation where I want to slow down (restrict) one user's bandwidth and prioritize all the other users. But if I make a rule that is specific to the user I want to restrict and a more general rule that covers everyone, then in order for the rules to work I have to put the more specific rule at the top, effectively putting the user I want to restrict in higher priority than the others.
If ordering mattered only for rule application, and each rule had a manually settable priority, then the system would be more flexible. I could have a pool for a single address, 5kb max bandwidth, and manually have the priority be low with this rule at the top of the list (remember order wouldn't matter as far as priority). Then below that rule I could have a catch all rule for anyone on the internal network with 100kb minimum bandwidth and the priority set manually to high.
I can accomplish the same thing now but because of the effect of ordering I'd have to make more rules.
Guest User!
You are not Sophos Staff.