ghkrauss last edited by
I have fq-codel configured and running. I do have errors related to ""Flowset Busy". I have been reading for last few weeks various postings with respect to the issues surrounding this problem. I have been unable to discern if the issue is a software bug or if a configuration fix will will resolve the matter. The discussion seems to wander. Has anyone come to a conclusion?
From @jimp (reddit, not the forums though). https://www.reddit.com/r/PFSENSE/comments/9j1h8u/244_codel_limiter_error/
It's harmless log spam as far as we've been able to tell so far. Thus, there is no proper fix. I think someone on the forum spotted the place where it happens but I haven't seen a patch yet.
So the fix for now is to ignore it or switch to an alternate QMA.
uptownVagrant last edited by
@ghkrauss No need to use CoDel on the child queue when FQ-CoDel is being used as the scheduler. Removing CoDel from the queue removes the flowset busy error. If you are interested in using FQ-CoDel I highly recommend this post which gives a detailed example of how to set it up properly. https://forum.netgate.com/post/807490
The "flowset busy" error is documented here by the person who actually implemented FQ-CoDel into ipfw/dummynet. https://forum.netgate.com/post/803118
Here is a post confirming that you don't need to set CoDel on the child queue as it won't be used with FQ-CoDel. https://forum.netgate.com/post/804118
ghkrauss last edited by ghkrauss
Thanks for the assistance. The issue is now fixed. With the new floating rules the NAT, IPV4 does not break the policy rules.