Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: Frantisek Borsik <frantisek.borsik@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: [Cake] Re: [Bloat] CAKE in IPFire (a professional-grade open-source firewall and security platform )
Date: Fri, 6 Feb 2026 10:16:19 +0000	[thread overview]
Message-ID: <64784DD5-350F-42ED-BBF9-F1A2854AC56D@ipfire.org> (raw)
In-Reply-To: <CAJUtOOiE=nVxqx1aFtP7mJZZxp+eDerdsNroQh6jrj7tq0n+tQ@mail.gmail.com>

Hello Frantisek,

I am glad to have seen your email.

I am Michael and the founder of IPFire, so if you have any questions, feel free to reach out.

We have been a very early adopter for anything Bufferbloat and I have been trying to support Dave as much as possible. We have been running some bechmarks and validating that fq_codel as it was proposed and implemented in the Linux kernel works, and the results were obviously overwhelming. Within a couple of releases, fq_codel was enabled by default, and there was virtually no way to disable it any more because nobody ever would want to have slow internet ever again.

I wrote a little blog post:

  https://www.ipfire.org/blog/ipfire-2-13-tech-preview-fighting-bufferbloat

And two articles in the German computer magazine c’t in 2013 - how time flies:

  https://www.ipfire.org/blog/ipfire-in-c-t-magazine-20-13

It seems that the links are no longer loading to the article for me :(

Since then we have of course migrated to a mix of fq_codel and CAKE and there have been a couple of researchers posting articles on benchmarking various firewall distros where IPFire always scores really well - if not winning - and a lot of that is thanks to fighting Bufferbloat and us being smart in how we arrange our firewall rules.

Of course IPFire is totally free, so give it a try!

Best,
-Michael

> On 5 Feb 2026, at 17:42, Frantisek Borsik <frantisek.borsik@gmail.com> wrote:
> 
> https://www.ipfire.org/docs/configuration/services/qos
> 
> Found out about it by chance, so did a search on the bufferbloat lists and
> found this mention in 2015, from Dave <3
> 
> https://lists.bufferbloat.net/cake/CAA93jw7VgnQb-_dBqQA0Ki7c56K=H6=DdTnTFjffUvwK_JGKgQ@mail.gmail.com/
> 
> 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
> _______________________________________________
> Bloat mailing list -- bloat@lists.bufferbloat.net
> To unsubscribe send an email to bloat-leave@lists.bufferbloat.net


  reply	other threads:[~2026-02-06 10:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 17:42 [Cake] CAKE in IPFire (a professional-grade open-source firewall and security platform ) Frantisek Borsik
2026-02-06 10:16 ` Michael Tremer [this message]
2026-02-06 13:16   ` [Cake] Re: [Bloat] " Frantisek Borsik

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=64784DD5-350F-42ED-BBF9-F1A2854AC56D@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=frantisek.borsik@gmail.com \
    /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