From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: David Lang <david@lang.hm>, m@jaap.pro
Cc: "cake@lists.bufferbloat.net" <cake@lists.bufferbloat.net>
Subject: [Cake] Re: help request for cake on a large network
Date: Sun, 28 Sep 2025 14:56:30 +0200 [thread overview]
Message-ID: <CAJUtOOj-FfPic8FPjy-QneCsvbtwtn4Zsxs+1yEsUqytEOEheg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.2509280523210.14652@nftneq.ynat.uz>
Jaap - thank you very much for recommending LibreQoS.
Yes, besides a typical last-mile ISP scenario, LibreQoS is being used in
various other setups, like to help with event Wi-Fi - here is one of the
deployments https://libreqos.io/2023/11/13/success-story-raceway/
To brag a little, other deployment scenarios we see are data centers,
cruise ships, university campuses, even mines :)
All the best,
Frank
Frantisek (Frank) Borsik
*In loving memory of Dave Täht: *1965-2025
https://libreqos.io/2025/04/01/in-loving-memory-of-dave/
https://www.linkedin.com/in/frantisekborsik
Signal, Telegram, WhatsApp: +421919416714
iMessage, mobile: +420775230885
Skype: casioa5302ca
frantisek.borsik@gmail.com
On Sun, Sep 28, 2025 at 2:38 PM David Lang <david@lang.hm> wrote:
> I guess I didn't give enough info on our network architecture.
>
> The upstream ISP is between 500Mb and 1G.
>
> We disconnect the conference center firewall and connect our firewall in
> it's
> place (Linux system)
>
> This border router connect to the conference center firewall (so their
> offices
> still get connectivity), and to two routers (Linux, one per building) that
> are
> also direct connected (a triangle between the three routers. The border
> router
> is doing NAT for IPv4 and MSS squashing for IPV6 that goes out through a
> tunnel
> (google doesn't do PMTU discovery on IPv6)
>
> (we are currently debating between deploying OSPF between the three
> routers, or
> just giving them static routes, high priority direct and low priority for
> the
> indirect path)
>
> Each building router then connects to one or a few switches in different
> closets
> that then go to a switch in each room (trunked ports).
> We hve a handful of wired users, 120APs for the users, and AV equipment
> for each
> of the 16 tracks that are recorded and streamed.
>
> a quick look at libreqos and it's pushing for a more complex network
> layout that
> will be a hard sell at least this year (last year our juniper routers fell
> over
> under the MSS squashing load for IPv6, so we are going to Linux systems
> this
> year, getting people to consider cake is hard enough, let alone another
> middleware box)
>
> David Lang
>
> On Sun, 28 Sep 2025, Jaap de Vos wrote:
>
> > Date: Sun, 28 Sep 2025 14:12:24 +0200 (CEST)
> > From: Jaap de Vos <m@jaap.pro>
> > Reply-To: "cake@lists.bufferbloat.net" <cake@lists.bufferbloat.net>
> > To: David Lang <david@lang.hm>, cake@lists.bufferbloat.net
> > Subject: Re: [Cake] help request for cake on a large network
> >
> > 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
> >
> _______________________________________________
> Cake mailing list -- cake@lists.bufferbloat.net
> To unsubscribe send an email to cake-leave@lists.bufferbloat.net
>
next prev parent reply other threads:[~2025-09-28 12:55 UTC|newest]
Thread overview: 11+ 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
2025-09-28 12:38 ` David Lang
2025-09-28 12:56 ` Frantisek Borsik [this message]
2025-09-28 17:07 ` dave seddon
2025-09-28 17:26 ` David Lang
2025-09-30 5:18 ` Jonathan Morton
2025-09-30 3:55 ` Jonathan Morton
2025-09-30 4:30 ` dave seddon
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=CAJUtOOj-FfPic8FPjy-QneCsvbtwtn4Zsxs+1yEsUqytEOEheg@mail.gmail.com \
--to=frantisek.borsik@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=david@lang.hm \
--cc=m@jaap.pro \
/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