interfaces-cake-ingress(5)

📦 version 0.13.0, in alpine 3.24

💅 interfaces-cake-ingress(5) — the CAKE ingress glow-up

okay so real talk: this is a page from the File Formats Manual, and it's all about interfaces-cake-ingress — the CAKE ingress extensions for the interfaces(5) file format. yes bestie, the whole interfaces vibe. let's get into it 🎀

✨ NAME ✨

interfaces-cake-ingress — CAKE ingress extensions for the interfaces(5) file format 🦋

🧁 DESCRIPTION 🧁

so. CAKE stands for Common Applications Kept Enhanced (iconic acronym, no notes), and it's a shaping-capable queue discipline that uses both AQM and FQ. yes, both. overachiever behavior, we love to see it 💅

what this extension does: it creates an IFB (Intermediate Functional Block) interface and links it to an existing logical interface — all so the CAKE qdisc can actually be applied to ingress traffic. like, traffic coming in. the incoming vibes. 🫶

and in most applications, you'd pair this extension with the interfaces-cake(5) extension to configure the qdisc that gets applied to ingress traffic. they're a duo. a package deal. main character + bestie energy 👑

also important: the cake-ingress extension only has one parameter, and it is mandatory. not optional. not "if you feel like it." mandatory mandatory. periodt 💀

🎀 CAKE-INGRESS OPTIONS 🎀

  • cake-ingress-dev interface_name — the underlying logical interface that this IFB should be connected to. that's it, that's the whole option list, she's simple and she knows what she wants 💖

🌈 EXAMPLES 🌈

🌸 Minimal configuration 🌸

the bare-minimum slay. here's what it looks like:

           auto foo foo-ifb
           iface foo
                use cake

           iface foo-ifb
                use cake
                cake-ingress true
                use cake-ingress
                cake-ingress-dev foo

🦋 Typical configuration 🦋

okay this one is lowkey the fun one. this config shapes egress traffic to 512 Mbps and ingress traffic to 1 Gbps, while applying docsis (cable modem) overhead compensation in both directions 🧚

and here's the key detail — as you can see here, the CAKE parameters for the ingress and egress traffic can totally have different parameters. two directions, two whole personalities. they don't have to match and that's the point ✨

           auto foo foo-ifb
           iface foo
                use cake
                cake-bandwidth 512Mbit
                cake-overhead docsis

           iface foo-ifb
                use cake
                cake-bandwidth 1Gbit
                cake-overhead docsis
                cake-tins besteffort
                cake-ingress true
                use cake-ingress
                cake-ingress-dev foo

👀 SEE ALSO 👀

go read those next, iykyk 💜

ngl, if you're doing ingress shaping without the interfaces-cake(5) extension in the mix, you're kinda doing it the hard way. just saying 🫶

and that's the page!! mwah 💋 this beauty is dated 2026-05-10 and she lives under interfaces-cake-ingress(5) — catch you in the next manpage, bestie 🌟🍓

📦 where this page comes from