Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Hesham ElBakoury <helbakoury@gmail.com>
To: David Lang <david@lang.hm>
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>,
	 Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Main hurdles against the Integration of Satellites and Terrestial Networks
Date: Mon, 18 Sep 2023 16:32:27 -0700	[thread overview]
Message-ID: <CAFvDQ9rWt=5jy0bpusPW6AVVQm7QfKzMDyWPD7MYRBVys8Z0pQ@mail.gmail.com> (raw)
In-Reply-To: <2sp89904-o460-976s-4rsq-55nn6ps84464@ynat.uz>

[-- Attachment #1: Type: text/plain, Size: 3291 bytes --]

Given the discussions in this email thread, what IETF should standardize in
priority order  for the integrated NTN terrestrial networks?

Thanks,
Hesham

On Sun, Sep 17, 2023, 12:59 PM David Lang via Starlink <
starlink@lists.bufferbloat.net> wrote:

> it's very clear that there is a computer in the dishy that you are talking
> to.
> You get the network connection while the dishy is not connected to the
> satellites (there's even a status page and controls, stowing and unstowing
> for
> example)
>
> I think we've seen that the dishy is running linux (I know the routers run
> an
> old openwrt), but I don't remember the details of the dishy software.
>
> David Lang
>
>   On Sun, 17 Sep 2023, Alexandre Petrescu via Starlink wrote:
>
> > Date: Sun, 17 Sep 2023 19:21:50 +0200
> > From: Alexandre Petrescu via Starlink <starlink@lists.bufferbloat.net>
> > Reply-To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
> > To: starlink@lists.bufferbloat.net
> > Subject: Re: [Starlink] Main hurdles against the Integration of
> Satellites and
> >      Terrestial Networks
> >
> >
> > Le 16/09/2023 à 01:32, Ulrich Speidel via Starlink a écrit :
> >> On 16/09/2023 5:52 am, David Lang wrote:
> >>>
> >>> In addition to that Ulrich says, the dishy is a full computer, it's
> >>> output is ethernet/IP and with some adapters or cable changes, you
> >>> can plug it directly into a router.
> >>
> >> We've done that with the Yaosheng PoE Dishy adapter - actually plugged
> >> a DHCP client straight in - and it "works" but with a noticeably
> >> higher rate of disconnects.
> >
> > It is good to know one can plug a DHCP client into the Ethernet of the
> > DISHY and receive DHCP replies.
> >
> > But that would be only a lead into what kind of DHCPv4 is supported, or
> not.
> >
> > I would ask to know whether the DHCP server runs on the DISHY, or
> > whether it is on the ground network of starlink, i.e. the reply to DHCP
> > request comes after 50ms, or after 500microseconds (timestamp difference
> > can be seen in the wireshark run on that Ethernet).
> >
> > This (DHCP server daemon on dishy or on ground segment) has an impact of
> > how IPv6  can be, or is, made to work.
> >
> > This kind of behaviour of DHCP - basically asking who allocates an
> > address - has seen a continous evolution in 3GPP cellular networks since
> > they appeared.  Nowadays the DHCP behaviour is very complex in a 3GPP
> > network; even in a typical smartphone there are intricacies about where
> > and how the DHCP client and server works. With it comes the problem of
> > /64 in cellular networks (which some dont call a problem, but I do).
> >
> > So, it would be interesting to see whether starlink has the same /64
> > problem as 3GPP has, or is free of it (simply put: can I connect several
> > Ethernet subnets in my home to starlink, in native IPv6 that is, or
> not?).
> >
> > Alex
> >
> > _______________________________________________
> > Starlink mailing list
> > Starlink@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/starlink
> >_______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>

[-- Attachment #2: Type: text/html, Size: 4632 bytes --]

  reply	other threads:[~2023-09-18 23:32 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 12:10 Hesham ElBakoury
2023-08-30 13:57 ` Alexandre Petrescu
2023-08-30 16:51   ` Inemesit Affia
2023-08-30 19:35     ` David Lang
2023-09-01 16:27       ` Inemesit Affia
2023-09-15 11:29         ` Alexandre Petrescu
2023-09-15 15:18           ` Ulrich Speidel
2023-09-15 17:52             ` David Lang
2023-09-15 23:32               ` Ulrich Speidel
2023-09-17 17:21                 ` Alexandre Petrescu
2023-09-17 19:58                   ` David Lang
2023-09-18 23:32                     ` Hesham ElBakoury [this message]
2023-09-19  0:31                       ` David Lang
2023-09-19  0:36                         ` Hesham ElBakoury
2023-09-19  1:01                           ` David Lang
2023-09-19  1:08                             ` [Starlink] [Sat-int] " Jorge Amodio
2023-09-19  1:25                               ` David Lang
2023-09-21  7:58                               ` emile.stephan
2023-09-21 12:37                               ` Alexandre Petrescu
2023-09-19 13:44                           ` [Starlink] " Alexandre Petrescu
2023-09-19 14:36                             ` David Lang
2023-09-19 13:35                       ` Alexandre Petrescu
2023-09-19 14:44                         ` David Lang
2023-09-17 17:12               ` Alexandre Petrescu
2023-09-17 17:09             ` Alexandre Petrescu
2023-09-17 18:06               ` Steve Stroh
2023-08-31  8:44     ` Alexandre Petrescu
2023-08-31 11:39       ` David Lang
  -- strict thread matches above, loose matches on Subject: below --
2023-10-16 13:26 David Fernández
2023-10-18 15:04 ` Alexandre Petrescu
2023-09-19 14:55 David Fernández
2023-09-19 15:15 ` David Lang
2023-09-20  8:09   ` Alexandre Petrescu
2023-09-20  8:32     ` David Lang
2023-09-03  1:03 David Fernández
2023-09-03  3:44 ` Mike Puchol
2023-09-15 11:35 ` Alexandre Petrescu
2023-08-31 16:12 David Fernández
2023-08-31 15:51 David Fernández
2023-08-30 12:02 Hesham ElBakoury

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='CAFvDQ9rWt=5jy0bpusPW6AVVQm7QfKzMDyWPD7MYRBVys8Z0pQ@mail.gmail.com' \
    --to=helbakoury@gmail.com \
    --cc=alexandre.petrescu@gmail.com \
    --cc=david@lang.hm \
    --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