Remember me. Post Reply Print view. I'd dearly like support for that in mikrotik given how problematic CS1 proved to be, and it's a teeny patch. I would really like it if people put it through a battery of flent rrul tests or heavy iperf, and took captures, and plotted rtts, particularly on the higher end mikrotik hw.
It is most useful with working BQL in the device driver. When using the shaper component, below 1gbit, gro "super"packets are automatically split up back into packets and then interleaved with other flows , when unshaped, or above 1gbit, they are not. If you've got the cpu, split up superpackets.
This does not work with some forms of offloaded nat. Exposing these statistics to more users would drive understanding of the role of packet loss and marking in controlling network delay. See the enthusiasm for collecting stats over in the starlink community I would love to see at the very least, drop stats out of the mikrotik userbase. I mean that. Impossible to get some forms of dsl right unless you compensate.
To save on cpu further, don't use the ack-filter or nat options. This a pretty heavy hammer, and it is preferred that y'all communicate with your customers about how you treat diffserv and let them optimize their own traffic, only remarking from 0 best effort to something else if you need to.
There is a published guide to zoom traffic, among others. Wash on egress if you aren't following the relevant RFCs. I should stress that these are options and are optional, aside from getting shaped dsl compensation right, the cake defaults are pretty good. We are very interested in feedback as to how to make it, or something like it, better for ISPs.
