Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Nathan Owens <nathan@nathan.io>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] teardown of the starlink provided "router"
Date: Tue, 18 May 2021 09:32:17 -0700	[thread overview]
Message-ID: <CAA93jw6b_7+V94a8n_0UE3-wFiZz9wey_1ndayLTv5zfPrT52A@mail.gmail.com> (raw)
In-Reply-To: <CALjsLJtwen6bakUhsufba1NG330eBPwy9zChpJPq25uj+J5HNg@mail.gmail.com>

On Tue, May 18, 2021 at 8:28 AM Nathan Owens <nathan@nathan.io> wrote:
>
> Here are the chips in the dish:
> https://twitter.com/VirtuallyNathan/status/1331709138276024320
> There's a bunch of the black ones, some sort of RF chip, and one of the heat-spreader capped ones. Parts seem to be custom, nothing I could find online.
>
> The Dish acts as the modem, so any router can be used. How were you testing? With their router? Without?

behind their router.

this explains my issues with ipv6, and at least some, with
bufferbloat. We will toss the starlink router over the cliff
soon and start over.
>
>
> On Tue, May 18, 2021 at 8:23 AM Nathan Owens <nathan@nathan.io> wrote:
>>
>> Here ya go: https://fcc.report/FCC-ID/2AWHPR201/4805890
>> There's at least one teardown video, but the FCC pics are better.
>>
>> Qualcomm IPQ4018, can run OpenWrt 19.07.7, or the latest 21.02.1 RC branch.
>>
>> --Nathan
>>
>> On Tue, May 18, 2021 at 8:20 AM Dave Taht <dave.taht@gmail.com> wrote:
>>>
>>> I would really like someone to disassemble, and take photographs of
>>> the chipset and design of the starlink provided "router",
>>> which is proving to be such a disaster, and put those up somewhere.
>>> Youtube videos seem to be popular... we could do a
>>>  kvetchy one of those?
>>>
>>> I have really goofed in that my visit to the starlink site I'd assumed
>>> the dishy was all there was! At one level I'm deliriously happy
>>> that that router can be junked, and with a decent OS, ipv6 etc can be
>>> enabled, as well as many other interesting local
>>> networking services. At another level I'm grumpy as to have to throw
>>> out all the bufferbloat related testing to date.
>>>
>>> In my dream world, the dishy would do ethernet flow control at a
>>> "single transmit upstream buffer" granularity, below 4ms, and
>>> emit pause frames that an fq_codel upstream could deal with, but that
>>> still is not enough, accurate parsing of the dishy's actual link rates
>>> up and down would allow for controlling the sch_cake queues tighter.
>>>
>>> --
>>> Latest Podcast:
>>> https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/
>>>
>>> Dave Täht CTO, TekLibre, LLC
>>> _______________________________________________
>>> Starlink mailing list
>>> Starlink@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/starlink



-- 
Latest Podcast:
https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/

Dave Täht CTO, TekLibre, LLC

      reply	other threads:[~2021-05-18 16:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18 15:20 Dave Taht
2021-05-18 15:23 ` Nathan Owens
2021-05-18 15:28   ` Nathan Owens
2021-05-18 16:32     ` 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=CAA93jw6b_7+V94a8n_0UE3-wFiZz9wey_1ndayLTv5zfPrT52A@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --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