Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Nils Andreas Svee <me@lochnair.net>
To: Pete Heist <pete@heistp.net>
Cc: dave seddon <dave.seddon.ca@gmail.com>,
	CAKE list <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Ubiquity (Unifi ) Smart Queues
Date: Tue, 9 Jan 2024 16:39:55 +0100	[thread overview]
Message-ID: <65325791-A1D1-4E21-9F1D-D17737BCFF0F@lochnair.net> (raw)
In-Reply-To: <deed5fd13e38d17c8b6716f4fdad64cba896385b.camel@heistp.net>

[-- Attachment #1: Type: text/plain, Size: 2460 bytes --]

You’re unlikely to do any real harm though, but the warning is there cause you can potentially soft brick your router using it. I’ve run into that myself if I remember correctly, where after a firmware upgrade the kernel had slightly changed, so loading the sch_cake module caused it to panic. And I had it start through /config/scripts/post-config.d of course, so it would happen on every restart.

Nothing a factory reset won’t solve, but annoying when if you’re messing about remotely :)

As for USG, I think I used to have some binaries for those too. I do still have some old kernel sources for them laying around in a repo.
It’s been awhile, but I probably stopped building for those as it wasn’t as straightforward to keep up with the versions of the firmware.

Though frankly, I don’t plan on updating the sch_cake and tc binaries when new firmwares are released anymore, as they don’t publish the GPL archives on their webpage after the redesign, and they don’t respond to requests for them either by the looks of the forums. So if it breaks there’s not much I can do anymore.

Best Regards,
Nils Andreas Svee

> On Jan 3, 2024, at 14:44, Pete Heist via Cake <cake@lists.bufferbloat.net> wrote:
> 
> On Tue, 2024-01-02 at 10:59 -0800, dave seddon via Cake wrote:
>> I thought people might be interested to see what Ubiquity/Unifi is
>> doing with "Smart Queues" on their devices.  The documentation on
>> their website is not very informative.
>> <snip>
>> "Smart Queue" Implementation
>> 
>> Looks like they only apply tc qdiscs to the Eth2, and sadly this is
>> NOT cake, but fq_codel.
>> 
>> And cake isn't available :(
>> 
>> root@USG-Pro-4:~# tc qdisc replace dev eth0 cake bandwidth 100m rtt
>> 20ms
>> Unknown qdisc "cake", hence option "bandwidth" is unparsable
> 
> Hi Dave, there's a community contributed version of Cake for EdgeRouter
> devices that I've been using for years on production ER-X's:
> 
> https://community.ui.com/questions/Cake-compiled-for-the-EdgeRouter-devices/fc1ff27c-f321-4344-8737-fcc755cae8a2
> 
> I don't think that works for UniFi/USG devices, however, and one should
> note the disclaimer and be careful when installing it. Also, it must be
> re-installed after every upgrade.
> 
> Cheers,
> Pete
> 
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake


[-- Attachment #2: Type: text/html, Size: 2970 bytes --]

  reply	other threads:[~2024-01-09 15:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-02 18:59 dave seddon
2024-01-02 20:52 ` Sebastian Moeller
2024-01-02 21:15   ` dave seddon
2024-01-02 21:24     ` Sebastian Moeller
2024-01-02 21:57 ` Jonathan Morton
2024-01-03 13:44 ` Pete Heist
2024-01-09 15:39   ` Nils Andreas Svee [this message]
2024-01-09 15:59     ` Dave Taht
2024-01-09 16:05     ` Dave Taht
2024-01-09 16:47       ` dave seddon
2024-01-09 16:57       ` Nils Andreas Svee
2024-01-09 17:07         ` dave seddon
2024-01-09 17:17           ` Dave Taht
2024-01-09 23:28             ` Nils Andreas Svee
2024-04-29 21:55               ` dave seddon
2024-01-09 23:17           ` Nils Andreas Svee

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=65325791-A1D1-4E21-9F1D-D17737BCFF0F@lochnair.net \
    --to=me@lochnair.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.seddon.ca@gmail.com \
    --cc=pete@heistp.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