Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: "David Fernández" <davidfdzp@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] APNIC56 last week
Date: Fri, 22 Sep 2023 19:00:32 +0200	[thread overview]
Message-ID: <CAC=tZ0p0JsBtV_S4CUOcYUTrTpQ0OSFyrRBrqKDOnvKudFXN=w@mail.gmail.com> (raw)

Hi David,

Mike said each satellite has 3 ISL, two connecting to the satellites
in front and back in the same orbital plane, then a third one that can
point anywhere (almost):

https://lists.bufferbloat.net/pipermail/starlink/2022-September/001000.html?fbclid=IwAR0TaPTdxVEp5iVWxch91mjnDT7aKVaOXPmyOd93PBING29YBWy9SNbV278

Regards,

David

> Date: Fri, 22 Sep 2023 01:41:16 -0700 (PDT)
> From: David Lang <david@lang.hm>
> To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
> Cc: starlink@lists.bufferbloat.net
> Subject: Re: [Starlink] APNIC56 last week
> Message-ID: <1oor055r-p02p-3o25-9056-p257s819q308@ynat.uz>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> I believe that I read that STarlink has 5 lasers per sat. but whatever the
> number, it's a tiny number compared to the number of satellites that they
> have
> up there.
>
> As you are looking at 'trains', check their altitude. They aren't going to
> shuffle sats around much, it's expensive in terms of fuel and they are only
> allowed to provide service when they are in their proper orbits.
>
> We know the lasers are in operation as they are providing service to places
> more
> than one sat hop away from ground stations. We also know they have a lot of
> ground stations around to share the load.
>
> We have almost no details on the specific modules they are using, and none
> on
> what routing they are using.
>
> David Lang

             reply	other threads:[~2023-09-22 17:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-22 17:00 David Fernández [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-19  4:39 Ulrich Speidel
2023-09-20  1:13 ` Dave Taht
2023-09-23  1:33   ` Noel Butler
2023-09-23  1:47     ` Vint Cerf
2023-09-23  4:22       ` Noel Butler
2023-09-23  6:41         ` Gert Doering
2023-09-23 10:53         ` Ulrich Speidel
2023-09-23 11:28           ` Sebastian Moeller
2023-09-23 12:56             ` Ulrich Speidel
2023-09-25  4:40           ` Noel Butler
2023-09-25  5:00             ` Ulrich Speidel
2023-09-25  5:10               ` Hayden Simon
2023-09-25  5:51               ` Noel Butler
2023-09-23 12:08     ` Hesham ElBakoury
2023-09-24 18:30     ` Michael Richardson
2023-09-25  4:04       ` Noel Butler
2023-09-21 13:20 ` Alexandre Petrescu
2023-09-21 19:05   ` Inemesit Affia
2023-09-21 19:08     ` Dave Taht
2023-09-22  8:26     ` Alexandre Petrescu
2023-09-22  8:41       ` David Lang
2023-09-22 17:12         ` Michael Richardson
2023-09-22 17:26           ` David Lang
2023-09-22 18:52             ` Michael Richardson
2023-09-23 21:55         ` Larry Press
2023-09-24  2:46           ` Dave Taht
2023-09-24 12:00           ` Hesham ElBakoury
2023-09-25  7:46             ` Alexandre Petrescu
2023-09-25  8:59               ` David Lang
2023-09-25 12:30                 ` Frantisek Borsik

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='CAC=tZ0p0JsBtV_S4CUOcYUTrTpQ0OSFyrRBrqKDOnvKudFXN=w@mail.gmail.com' \
    --to=davidfdzp@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