From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
aesomerville@gmail.com
Subject: Re: [Cerowrt-devel] android, sqm-autorate and lte and videoconferencing
Date: Wed, 6 Apr 2022 22:38:58 +0200 [thread overview]
Message-ID: <FF5B1A66-0C98-466A-A65C-163D63C4B0D3@gmx.de> (raw)
In-Reply-To: <CAA93jw4LdU814uc4VKV35NkethEaxmTpUkP-hruY=QCEYXh1rg@mail.gmail.com>
Dear Dave, dear all
please, let me introduce Andrew to this list, who is the driving force behind CAKE-autorate's design and implementation (which started from a more theoretical discussion in the OpenWrt forum before turning into something tangible). There are other alternative approaches for the rate-tracking problem many discussed in this longish forum thread: https://forum.openwrt.org/t/cake-w-adaptive-bandwidth/108848 (which is great as this occasionally leads to quite interesting discussion about how the different teams tackle common issues) but Andrew's autorate appears to the fastest moving with low software requirements (every router should run bash anyway ;) ).
Kind Regards
Sebastian
> On Apr 6, 2022, at 17:43, Dave Taht <dave.taht@gmail.com> wrote:
>
> For the past several days, I have been very successfully using
> variants of the cake-autorate code to manage my connections on the
> boat, for which I use a tether to my laptop.
>
> https://github.com/lynxthecat/CAKE-autorate
>
> Although this test claims my link was inadequate for a good videoconference
>
> https://www.waveform.com/tools/bufferbloat?test-id=964831e5-30f9-4695-bfbd-b58da0a759f3
>
> they have all been perfect (and that test was conducted during an
> actual zoom conference). The code does not grab as much bandwidth as
> it could, when available, but I'll settle for perfect
> videoconferencing.
>
> Anyway... what I used to do was attach the phone to a router shared
> boat-wide that did this stuff, but it would be nice to move the
> algorithm directly into an android. My hope is that more modern
> androids are running a recent enough kernel(?) to have cake, but it's
> been a long time since I built anything for android, and am wondering
> if there is a lte/5g tablet or phone or dedicated lte router "out
> there" that can be hacked on?
>
>
>
> --
> I tried to build a better future, a few times:
> https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
>
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2022-04-06 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 15:43 Dave Taht
2022-04-06 20:38 ` Sebastian Moeller [this message]
2022-04-06 21:42 ` Dave Taht
2022-04-07 8:37 ` Andrew Somerville
2022-04-15 21:41 ` Joel Wirāmu Pauling
2022-04-17 5:27 ` [Cerowrt-devel] [Bloat] " Luis A. Cornejo
2022-04-20 10:29 ` Andrew Somerville
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FF5B1A66-0C98-466A-A65C-163D63C4B0D3@gmx.de \
--to=moeller0@gmx.de \
--cc=aesomerville@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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