Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Measuring the Satellite Links of a LEO Network
Date: Mon, 12 Feb 2024 15:13:52 +0100	[thread overview]
Message-ID: <5323051a-5835-4e42-9850-2f3349a8bd77@gmail.com> (raw)
In-Reply-To: <CAHn=e4hYtgVASbjGA0OCw+r0fvsRpareOVigO4noFMN+HjpS3w@mail.gmail.com>

this is an issue for 6MAN WG at IETF, but this is the text with the 
issue in the paper:

> From the user device or customer router at 192.168.1.1,
> we can reach its GS gateway at 100.64.0.1 (or equivalently
> fe80::200:5eff:fe00:101 for IPv6)

That IPv6 link-local address has an 'ff:fe' in it; the prefix is 'fe80' 
and the rest is an 'Interface ID', in RFC parlance.

That IID should be more random in its appearance.  It is called an 
'opaque' IID, and specified in RFC 7217 "Stable and Opaque IIDs with 
SLAAC" of year 2014.

That IPv6 address corresponds to earlier forms of these IIDs (RFC2464 of 
year 1998); they had that IID to be derived from a 48bit MAC address and 
inserted an 'ff:fe' string in it to become 64bit.

Most embedded linux platforms (v2.x kernels?) still use that ff:fe.  
Migrating these kernels is sometimes very difficult.  One might not want 
to migrate an kernel to a bloated and slower v3 or higher just for that 
little 'ff:fe'.  Maybe one wants to migrate just its IPv6 stack, but 
it's not easy.

The reason of making this IID more opaque is to resist scanning 
attacks.  A scanning attack is when a user might have somehow an 
illegitimate starlink terminal and tries to connect to the legitimate 
starlink network.  Part of that trying is to know the IP address of the 
next hop.  With IPv6 it comes down to testing all these addresses.  If 
they have a constant 'ff:fe' in them, it is easier to find them by brute 
force than if they were opaque.  It is also true that if in IPv4 that 
next hop is always the same then the easiest attack is to simply use 
IPv4 instead of IPv6.  But this 'opaqueness' of the IID in the IPv6 ll 
address might still be needed when IPv4 is get rid of.

This could be discussed at IETF, could be suggested to starlink to 
upgrade, etc.

Alex

Le 12/02/2024 à 07:59, J Pan via Starlink a écrit :
> http://pan.uvic.ca/webb/viewtopic.php?p=124670#p124670 to appear at
> ieee icc 2024. feedback welcome, especially during the camera-ready
> stage this week. thanks!  -j
> --
> J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink

  reply	other threads:[~2024-02-12 14:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12  6:59 J Pan
2024-02-12 14:13 ` Alexandre Petrescu [this message]
2024-02-13 17:12   ` J Pan
2024-02-13 17:39     ` Alexandre Petrescu
2024-02-13 17:43       ` Alexandre Petrescu
2024-02-13 17:44     ` Alexandre Petrescu
2024-02-13 18:11       ` Alexandre Petrescu
2024-03-03 10:23         ` Gert Doering
2024-03-04  8:39           ` Alexandre Petrescu

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=5323051a-5835-4e42-9850-2f3349a8bd77@gmail.com \
    --to=alexandre.petrescu@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