How to use the cake queue management system on the Turris Omnia

Keep those, unless you do not want them, they are considered the defaults… BUT really make sure to empty iqdisc_opts and eqdisc_opts before switching back to a non-cake qdisc, as otherwise sqm-scripts will fail to start-up and function properly, there is a reason why these are in the dangerous section of the GUI (one goal was to make the common thing easy and the more elaborate at least possible, and especially to allow to test and do things not considered at the time sqm-scripts was created).

Then again, these are defaults you might want to change:
SQUASH_DSCP this basically will remap incoming packet’s DSCP to the default 0
SQUASK_INGRESS this will ignore DSCP markings on incoming packets
These two are separate as the iptables based DSCP remapping unfortunately only happens after the ifb device, so sqm-scripts ingress shaper will see these markings no matter what.
INGRESS_ECN this will use ecn markings on incoming packets to signal explicit congestion notification using flows to slow down instead of throwing the packet away. EGRESS_ECN will do the same for outgoing packets. Since packets on the downstream typically already have passed the true bottleneck default to ECN marking as dropping those will neither signal congestion faster (but actually a tiny bit slower) nor will it speed up data delivery. On egress the default is noecn, as typically egress bandwidth is much lower so not sending a packet allows to keep the sent packet’s latency lower and since the packet still might be dropped along the path it is not really that certain that the ECN marking will actually help the sender react faster to the congestion event. Current opinion seems to be that with reasonable fast egress links (>=10Mbps?) ecn could also be used as default on egress, but I digress.

2 Likes