Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jaap de Vos <m@jaap.pro>
To: David Lang <david@lang.hm>, cake@lists.bufferbloat.net
Subject: [Cake] Re: help request for cake on a large network
Date: Sun, 28 Sep 2025 14:12:24 +0200 (CEST)	[thread overview]
Message-ID: <2064666241.42029.1759061544846@app.mailbox.org> (raw)
In-Reply-To: <alpine.DEB.2.02.2509280400350.14652@nftneq.ynat.uz>

Hi David,

I haven't tried it myself yet, but this sounds like a use case for which LibreQoS is suitable. However, LibreQoS would fit best if you can build something in line with the design assumptions: https://libreqos.readthedocs.io/en/latest/docs/v2.0/design.html
Specifically the part about putting it in between other routers and running a routing protocol with those.

There are some good recommendations around suitable hardware and sizing/scaling too: https://libreqos.readthedocs.io/en/latest/docs/v2.0/requirements.html

What kind of upstream bandwidth are you working with at the conference? I run the Mikrotik implementation of CAKE on a campsite. It really helps to get the most out of our asymmetrical gigabit coax line over there, no fiber available yet. So far, we got close to 500 devices on our outdoor Wi-Fi network with mostly good experiences, amazing. Before that, FQ_CoDel on PfSense worked well too, but the network wasn't as busy back then. I'd like to see CAKE on BSD some day.

Kind regards,
Jaap de Vos


> On 09/28/2025 1:06 PM CEST David Lang <david@lang.hm> wrote:
> 
>  
> I'm starting to prepare for the next Scale conference and we are switching from 
> Juniper routers to Linux routers. This gives me the ability to implement cake.
> 
> One problem we have is classes that tell everyone 'go download this' that 
> trigger hundreds of people to hammer the network at the same time (this is both 
> a wifi and a network bandwidth issue, wifi is being worked on)
> 
> The network is pretty flat, a couple of subnets each on ipv4 and ipv6.
> 
> Any suggestions on how to configure cake for this sort of environment where 
> there are so many devices?
> 
> David Lang
> _______________________________________________
> Cake mailing list -- cake@lists.bufferbloat.net
> To unsubscribe send an email to cake-leave@lists.bufferbloat.net

  parent reply	other threads:[~2025-09-28 12:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-28 11:06 [Cake] " David Lang
2025-09-28 12:10 ` [Cake] " Sebastian Moeller
2025-09-28 12:17   ` David Lang
2025-09-28 12:12 ` Jaap de Vos [this message]
2025-09-28 12:38   ` David Lang
2025-09-28 12:56     ` Frantisek Borsik
2025-09-28 17:07       ` dave seddon
2025-09-28 17:26         ` David Lang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2064666241.42029.1759061544846@app.mailbox.org \
    --to=m@jaap.pro \
    --cc=cake@lists.bufferbloat.net \
    --cc=david@lang.hm \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox