Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Nick Buraglio <nick@buraglio.com>
Cc: Dave Taht <dave.taht@gmail.com>, Starlink@lists.bufferbloat.net
Subject: Re: [Starlink] dhcpv6-pd details
Date: Mon, 17 May 2021 12:36:55 -0700 (PDT)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.2105171235160.7797@qynat-yncgbc> (raw)
In-Reply-To: <CAGB08_cKE54qDMkqX5T4S=TUA_CGuudtOt2pt10=jdRswD_m=A@mail.gmail.com>

On Mon, 17 May 2021, Nick Buraglio wrote:

> Inline
>
> On Mon, May 17, 2021 at 2:15 PM Dave Taht <dave.taht@gmail.com> wrote:
>>
>> Starlink provides a router, also? I'm so confused. I thought the dishy
>> was all there was. Care to tear it apart and describe what's in it?
>
> As far as the "router" is concerned, it's very much a consumer grade
> device that is managed via the mobile app. I hated it, so I took it
> out. It's still up in the attic. near the cable conduit, if I recall.

Fantastic, I was hoping it would be something like this. I think this opens up a 
lot of more useful options (including more easily doing failover between the 
dish and other network options)

David  Lang

  reply	other threads:[~2021-05-17 19:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17 18:58 Nick Buraglio
2021-05-17 19:15 ` Dave Taht
2021-05-17 19:30   ` Nick Buraglio
2021-05-17 19:36     ` David Lang [this message]
2021-05-17 19:48       ` Nick Buraglio
2021-05-17 19:59         ` Dave Taht
2021-05-17 21:02           ` Nick Buraglio
2021-05-17 23:56             ` Dave Taht
2021-05-18  2:21               ` Nick Buraglio
2021-05-18  6:51                 ` Gert Doering
2021-05-17 19:37   ` Nathan Owens
2021-05-18  8:33   ` Annika Wickert
2021-05-18 11:37     ` Nick Buraglio
2021-05-18 11:41       ` Annika Wickert
2021-05-18 14:48         ` Nick Buraglio
2021-05-18 14:50           ` Annika Wickert
2021-06-06  3:41             ` Darrell Budic

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=nycvar.QRO.7.76.6.2105171235160.7797@qynat-yncgbc \
    --to=david@lang.hm \
    --cc=Starlink@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=nick@buraglio.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