From: Dave Taht <davet@teklibre.net>
To: Nathan Owens <nathan@nathan.io>
Cc: Nils Andreas Svee <me@lochnair.net>,
starlink@lists.bufferbloat.net, Hauke Mehrtens <hauke@hauke-m.de>
Subject: Re: [Starlink] (udm pro) Was: Re: Does the dish run OpenWrt?
Date: Tue, 8 Jun 2021 16:37:15 -0700 [thread overview]
Message-ID: <BC13963A-A9EB-4940-864F-36A765F6E987@teklibre.net> (raw)
In-Reply-To: <CALjsLJt8rZZzZ5tNuNVvJB7ZrutOxTqe8BkOoA+uS71Z8DvUcg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]
It always had fq_codel (“smart queues”) but they buried it in the “old gui”. Their default bandwidth test doesn’t set it right and they missed scaling the quantum properly so it scaled to a gbit.
toss the sqm-scripts onto it…
lastly, sch_cake builds out of tree for linux versions as old as linux 3.10.
> On Jun 8, 2021, at 3:31 PM, Nathan Owens <nathan@nathan.io> wrote:
>
> Yep, I run the latest code:
> Linux Nathan-UDMP 4.19.152-al-linux-v10.2.0-v1.10.0-12.3672-bace201 #1 SMP Fri May 28 18:00:20 UTC 2021 aarch64 GNU/Linux
>
> At least it has fq_codel now...
>
> On Tue, Jun 8, 2021 at 3:29 PM Nils Andreas Svee <me@lochnair.net <mailto:me@lochnair.net>> wrote:
> Nice find!
>
> I guess someone finally managed to coax the kernel sources out of them. Still nothing on the download page, so I guess you got to reach out to them yourself if you'd like a copy.
>
> Are you on the beta firmware that got upgraded to kernel 4.19 Nathan? Wouldn't have high expectations of CAKE being enabled, but at least you won't have to backport.
>
> Either way the software on those things are a disappointment, so if I ever get one it'll be to run OpenWrt on (or just plain Alpine/Debian or similar).
>
> Best Regards
> Nils
>
[-- Attachment #2: Type: text/html, Size: 2558 bytes --]
prev parent reply other threads:[~2021-06-08 23:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <98e5e35f-dcca-0b1c-65c1-3da193779b5f@phrozen.org>
[not found] ` <d7409eb6-e972-ac74-36d0-ea5297c39ad0@hauke-m.de>
[not found] ` <95CC2CF3-6EBB-4F8F-AD2C-58E791459E8D@teklibre.net>
[not found] ` <701613ff-7a53-267f-77d0-a4e015b8410c@hauke-m.de>
[not found] ` <6A2BF4D0-EF5E-4256-AE95-B61F12200BD8@teklibre.net>
2021-06-08 21:52 ` Nathan Owens
2021-06-08 22:29 ` Nils Andreas Svee
2021-06-08 22:31 ` Nathan Owens
2021-06-08 23:37 ` Dave Taht [this message]
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BC13963A-A9EB-4940-864F-36A765F6E987@teklibre.net \
--to=davet@teklibre.net \
--cc=hauke@hauke-m.de \
--cc=me@lochnair.net \
--cc=nathan@nathan.io \
--cc=starlink@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