From: Andrew Crane <fairalbion@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] congestion control info off the datapath
Date: Wed, 28 Jul 2021 17:00:20 -0400 [thread overview]
Message-ID: <CAP4ODMdF-6s4sRYL7fPe5r_2NDA4YPrRi30NDB7_Ctp4F+6ncA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6FKvw-A8nH8Py5Np-dnt+NJ=gN0oYGBYoYTrXF3PLXKQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
< Please? newer folk here, please briefly introduce yourselves and your
< interests in starlink's stuff?
My story.
I'd moved from a suburban area, which had decent DOCSIS service, to a
remote rural area, where the choice was between woeful DSL service... or
nothing.
After a few weeks of pain, neighbors alerted me to a home router that
supposedly made life bearable. I'd encountered a lot of worthless IT snake
oil in my job & was skeptical. But I did some reading about bufferbloat,
threw skepticism to the wind, and bought the router.
It tuned itself to the connection and ended up making things workable. I'm
not a network engineer - my specialty was DNS/DHCP/IP address management -
but nerded out around the subject of latency under load. I ended up putting
together an OpenWRT-based home router.
When Starlink became operational, bufferbloat was the first thing I was
curious about, especially given the "back-to-first-principles" engineering
that Starlink aspires to.
~ Andrew
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
[-- Attachment #2: Type: text/html, Size: 1806 bytes --]
next prev parent reply other threads:[~2021-07-28 21:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-24 17:02 Dave Taht
2021-07-26 5:26 ` Ulrich Speidel
2021-07-28 21:00 ` Andrew Crane [this message]
2021-07-29 21:31 ` Michael Richardson
2021-07-29 14:57 ` Jared Mauch
2021-07-31 13:04 ` Srinivas Narayana
2021-08-11 17:59 ` Nick Buraglio
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=CAP4ODMdF-6s4sRYL7fPe5r_2NDA4YPrRi30NDB7_Ctp4F+6ncA@mail.gmail.com \
--to=fairalbion@gmail.com \
--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