Help me master the Smart Queue
Hi, I would like to have 3 Smart Queue rules to define traffic using Target Lists in each of the 3 Priority levels, My internet speed is 100mbit down / 40mbit up,
My general idea is pretty straight forward:
- High Priority rule = gaming traffic and VOIP - speed is capped to just under max bandwidth - traffic defined in a Target List called "High"
- Low Priority rule = download traffic, updates, cloud backups etc - speed is capped to 75mbit / 20mbit - traffic defined in a Target List called "Low"
- Default Priority rule = All traffic not defined in either the High or Low Lists - speed capped to just under max bandwidth - no Target List needed
I'm wondering if the above is the best way, my reasoning: if something is not specified in the High or Low rules then it goes to the Default rule, that way all traffic is processed by Smart Queue and I wont have some random uncapped traffic potentialy creating bufferbloat
I have a couple of questions however,
1. Since the Default rule will be Matching "All Traffic", and the High and Low rules will use separate "Target Lists", how can I make sure that the Target Lists get checked and applied before the Default rule of "All Traffic"
I noticed on your suport page for Smart Queue you have it stated:
When there is conflict:
the priority of different levels are device > group > network > global(All devices).
When there is conflict, device/group rules will take precedence over Network rules. When there is conflict, Network rules will take precedence over Global rules.
Does the above mean that I should put the Default rule into Global and the High and Low rules into Network? as I want the High and Low rules to be looked at first and have those priorities applied and all remaining connections fall down to the Global level and have Default applied?
2. Why are we specifying speed limits within the rules themselves?, typically in most QoS setups on other Router softwares, you specify what your internet bandwidth is down / up outside of the traffic rules and then you set the priorities on the traffic within the rules, optionally you can choose to have a reduction in speed for traffic matching the rule as a % of the bandwidth you specified. It just seems a little odd that with Firewalla if we want to set up 3 rules and for each of the rules there is no desired speed change, we are typing in the same speed 3 times. It also adds confusion in the sense that if the speed is additive, you shouldnt specify your max bandwidth more than once, as that will allow the rules to try and use more than your maximum physical bandwidth and lead to bufferbloat. I assume the speed limits in each rule is NOT additive, but this can lead to confusion here.
Thanks for advice in advance, enjoying my Purple!
-
QoS rules are very specific to your working/home environment; there is no right or wrong, it all depends on your application, so after you configure the rules and your network is better, then stick with it. And in general, the lesser rules you have the better, it makes debugging easier.
As of your rules, you shouldn't worry about the default, since it is just there. What you need to worry about is if you have conflicting configurations, and this is where the priority will come from. If you have no overlap of conflicting rules, you should be fine.
You don't have specify the bandwidth part, it is just there to make the UI simpler.
Please sign in to leave a comment.
Comments
1 comment