Fq_Codel UI
-
I cannot wait for this to be in pfSense. Then we can just make a sticky in the Traffic Shaping forum and tell everyone to use it.
-
You know something we don't?
-
I just assumed it was going to eventually happen
https://redmine.pfsense.org/issues/6620
Code is in 11.1 / 2.4.
https://svnweb.freebsd.org/base?view=revision&revision=300779GUI needs adaptation.
Assigned to Beaver so he can do the work, or re-assign to Jones or Pingle. (Or maybe a community member will do it.)
-
That should be a nice addition. Can't wait to try it out.
-
add me to that list
-
Looks like this got pushed back until at least 2.4.4 Makes sense. Lots of bugs fixed in 2.4.3 and no point delaying longer that needed. I would say that this one feature could almost warrant its own release if 2.4.4 starts taking too long. fq_codel is magic for the cares of most who use it. No rules, no priorities, just set your bandwidth and done for most situations.
-
Looks like this got pushed back until at least 2.4.4 Makes sense. Lots of bugs fixed in 2.4.3 and no point delaying longer that needed. I would say that this one feature could almost warrant its own release if 2.4.4 starts taking too long. fq_codel is magic for the cares of most who use it. No rules, no priorities, just set your bandwidth and done for most situations.
100% agree with you on this. There's only a handful of parameters that can be tweaked on the fq_codel algorithm and the performance (from what I've been able to test so far) is excellent given its simplicity. Including it in the GUI would really drive up adoption and we could then focus just on recommendations for tweaking parameters.
In the meantime, setting it up manually doesn't require all too much effort. All one needs to do is create a pair of limiters, with queues underneath them. Apply the queues to the appropriate firewall rules and then enable fq_codel for the queues using the CLI. The changes can easily be made persistent through reboots by using ShellCmd.
