fq_codel and cake-maint project starting up this month

I am starting up (with some funding from NLNET and comcast) a bufferbloat.net project as of this month to fix some outstanding bugs and add new features. It would be so great if mikrotik would throw in some dough (and gear) for development and testing also.

To this day I do not know what, if any, fq_codel or cake features made it into routerOS after the kernel you are using - be it some l4s support, or anything presently out of tree in the cakemq project: https://docs.google.com/document/d/1tTYBPeaRdCO9AGTGQCpoiuLORQzN_bG3TAkEolJPh28/edit#heading=h.vbbnfu73wlpp

But, as I have done for other router vendors, be willing to supply backports to y’all if you want, and can test (and ideally, participate or help pay for ongoing development. Also - to your userbase - what features do you need?

My principal kvetch last year was that queue trees are inefficient compared to just using cake´s integral shaper for both up and down. Also BQL?

Script-les (ie built-in) auto-adjustment of fluctuating connection speed like LTE/NR etc. Thanks! :smiley:

Regarding driver queues and counters, MTs’ tailor-made variants probably need to be reviewed in the event of a transition to BQL. But in the long run, I believe it will be beneficial to standardize this.

Need a series of tests and configurations. No one has come out and proven anything yet. Would like to see example setups and recommendations for really common scenarios. Make something like this and prove a configuration.

Yeah, a bunch of “best practice” configurations for some common use cases would definitely help a lot of people. Like Cake Recipes for ROS. Especially since CAKE is supposed to be easy to get started with but has tons of options.

It seems like your writing is addressed to mikrotik. This is a community forum. If I am not wrong, none of Mikrotik staff ever commented to your high quality topics in this forum. I suggest to address inquiries directly to support@mikrotik.com or sales@mikrotik.com to get proper attention.

Correct suggestion !