From: David Lang <david@lang.hm>
To: cake@lists.bufferbloat.net
Subject: [Cake] help request for cake on a large network
Date: Sun, 28 Sep 2025 04:06:32 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.2509280400350.14652@nftneq.ynat.uz> (raw)
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
next reply other threads:[~2025-09-28 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 11:06 David Lang [this message]
2025-09-28 12:10 ` [Cake] " Sebastian Moeller
2025-09-28 12:17 ` David Lang
2025-09-28 12:12 ` Jaap de Vos
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=alpine.DEB.2.02.2509280400350.14652@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=cake@lists.bufferbloat.net \
/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