CoDel Pass Rule floating to the top?
-
I've setup traffic shaping and frequently notice that it stops working - everything seems to drop onto the default queue. When I check things out, I notice that my CoDel rule (which according to the documentation should be at the bottom of the list) has floated to the top. As a result, it's "quick" and traffic shaping seems to stop.
Am I missing something? If I put the rule back at the bottom, traffic shaping starts again, but then it will randomly (I cannot find a reason!) float back to the top.
Can I run a CoDel queue alongside traffic shaping? Or should I not be running a CoDel limiter alongside traffic shaping?
-
@majic79 Do you have pfBlocker? That can reorder rules per its settings. Though I haven’t used that with floating rules, and I generally use Alias Native and create my own rules.
-
Use Limiter Rules with Match and uncheck quick.
-
@steveits - I do have pfBlocker - I'll double check that setup, thanks
-
@nocling @steveits - just want to say thank you, yes, it looks like PfBlockerNG is re-ordering the rules and making adjustments I didn't want. Moving the rule from pass to match (and removing quick) seems to work fine and hopefully it won't fall foul of pfBlocker re-ordering the rules (will see what happens tomorrow when the rules reload tonight)
-
I use this Rule Order:
-
@nocling yep - I'm using the same rule order. I think the "Pass" option for CoDel (in the documentation) meant that it gets re-ordered to the top of the list when it should be the last thing. I've put it at the end of my list of traffic shaping "match" rules and bufferbloat tests seem consistent in behaviour to the "pass" rule at the end of all floating rules.