Compensates for ATM cell framing, which is normally found on ADSL links.

Automatic capacity estimation based on traffic arriving at this qdisc

CAKE can divide traffic into "tins" based on the Diffserv field:

• diffserv4 Provides a general-purpose Diffserv implementation with four tins: Bulk (CS1), 6.25% threshold, generally low priority. Best Effort (general), 100% threshold. Video (AF4x, AF3x, CS3, AF2x, CS2, TOS4, TOS1), 50% threshold. Voice (CS7, CS6, EF, VA, CS5, CS4), 25% threshold.

• diffserv3 (default) Provides a simple, general-purpose Diffserv implementation with three tins: Bulk (CS1), 6.25% threshold, generally low priority. Best Effort (general), 100% threshold. Voice (CS7, CS6, EF, VA, TOS4), 25% threshold, reduced Codel interval.

• flowblind - Disables flow isolation; all traffic passes through a single queue for each tin.
• srchost - Flows are defined only by source address. 
• dsthost Flows are defined only by destination address. 
• hosts - Flows are defined by source-destination host pairs. This is host isolation, rather than flow isolation.
• flows - Flows are defined by the entire 5-tuple of source address, a destination address, transport protocol, source port,and destination port. This is the type of flow isolation performed by SFQ and fq_codel.
• dual-srchost Flows are defined by the 5-tuple, and fairness is applied first over source addresses, then over individual flows. Good for use on egress traffic from a LAN to the internet, where it'll prevent anyone LAN host from monopolizing the uplink, regardless of the number of flows they use.
• dual-dsthost Flows are defined by the 5-tuple, and fairness is applied first over destination addresses, then over individual flows. Good for use on ingress traffic to a LAN from the internet, where it'll prevent anyone LAN host from monopolizing the downlink, regardless of the number of flows they use.
• triple-isolate - Flows are defined by the 5-tuple, and fairness is applied over source *and* destination addresses intelligently (ie. not merely by host-pairs), and also over individual flows.
• nat Instructs Cake to perform a NAT lookup before applying flow- isolation rules, to determine the true addresses and port numbers of the packet, to improve fairness between hosts "inside" the NAT. This has no practical effect in "flowblind" or "flows" modes, or if NAT is performed on a different host.
• nonat (default) The cake will not perform a NAT lookup. Flow isolation will be performed using the addresses and port numbers directly visible to the interface Cake is attached to.

Limit the memory consumed by Cake to LIMIT bytes. By default, the limit is calculated based on the bandwidth and RTT settings.

Rounds each packet (including overhead) up to a minimum length BYTES. 

Instructs Cake to perform a NAT lookup before applying a flow-isolation rule.

Adds BYTES to the size of each packet. BYTES may be negative.

Manually specify an RTT. Default 100ms is suitable for most Internet traffic.

• datacentre - For extremely high-performance 10GigE+ networks only. Equivalent to RTT 100us.
• lan - For pure Ethernet (not Wi-Fi) networks, at home or in the office. Don't use this when shaping for an Internet access link. Equivalent to RTT 1ms.
• metro - For traffic mostly within a single city. Equivalent to RTT 10ms. regional For traffic mostly within a European-sized country. Equivalent to RTT 30ms.
• internet (default) This is suitable for most Internet traffic. Equivalent to RTT 100ms.
• oceanic - For Internet traffic with generally above-average latency, such as that suffered by Australasian residents. Equivalent to RTT 300ms.
• satellite - For traffic via geostationary satellites. Equivalent to RTT 1000ms.
• interplanetary - So named because Jupiter is about 1 light-hour from Earth. Use this to (almost) completely disable AQM actions. Equivalent to RTT 3600s.

Apply the wash option to clear all extra DiffServ (but not ECN bits), after priority queuing has taken place.