From: David Lang <david@lang.hm>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: Sebastian Moeller <moeller0@gmx.de>,
Steven <bufferbloat-lists@steven.honson.au>,
starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Info on IP country ranges
Date: Wed, 13 Dec 2023 10:27:09 -0800 (PST) [thread overview]
Message-ID: <4rooss86-p114-8qp1-38r8-rn4302n99or4@ynat.uz> (raw)
In-Reply-To: <fb69a150-e82a-48f5-8d8d-02142ba88e7a@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2036 bytes --]
On Wed, 13 Dec 2023, Alexandre Petrescu via Starlink wrote:
> A tunnel within 3GPP network (GTP) is used, among other reasons, to
> support mobility. The 'mobility', among some interpretations, is to
> maintain a constant IP address for a moving end user.
>
> Surprisingly, the URL
> https://support.starlink.com/?topic=1192f3ef-2a17-31d9-261a-a59d215629f4
> explains that that kind of mobility is not supported in starlink, i.e.
> the end user might get another IP address if going to some other area.
> It is surprising in that in other starlink.com URLs they offer starlink
> service for automobiles, and these typically move a lot. Maybe the
> starlink-connected automobiles do change their IP addresses a lot, but
> the end users dont care that much.
>
> To support mobility within a starlink network - maintain constant all IP
> addresses in a car - maybe one would try the DHCPv6 CONFIRM message to
> try to maintain the same allocated /56 but it another area. Maybe the
> starlink DHCPv6-PD server will satisfy that CONFIRM, or maybe not.
>
> Or maybe there is a need of some other protocol in starlink, or in user
> equipment connected to starlink (Dishy, third party router), to offer
> that mobility. But without adding new latency, of course.
>
> (this mobility aspect is on topic of the IP country ranges -
> cross-border areas would ideally not break connectivity).
There are two types of keeping your address. One is to have the same address all
the time, the other is to keep your address during a session.
Even if you get a public address, it can change from time to time (just like
DHCP addresses could on landline ISPs), but that doesn't mean that your address
will change during a session (i.e. while you are powered up and connected) even
while moving around.
If you get a public IP, that IP will change like a DHCP address would on a
landline ISP, rarely and mostly when equipment at one end or another was
restarted, but not every time you do a new satellite handoff
David Lang
next prev parent reply other threads:[~2023-12-13 18:27 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 0:15 Noel Butler
2023-12-04 0:44 ` J Pan
2023-12-04 12:04 ` Noel Butler
2023-12-04 18:17 ` J Pan
2023-12-07 11:54 ` Alexandre Petrescu
2023-12-07 18:07 ` J Pan
2023-12-07 20:10 ` Alexandre Petrescu
2023-12-07 20:40 ` David Lang
2023-12-08 5:57 ` Freddie Cash
2023-12-08 8:30 ` Alexandre Petrescu
2023-12-08 8:37 ` Alexandre Petrescu
2023-12-08 15:27 ` Freddie Cash
2023-12-08 17:26 ` Alexandre Petrescu
2023-12-08 8:40 ` Steven
2023-12-08 10:22 ` Alexandre Petrescu
2023-12-08 10:31 ` Steven
2023-12-08 11:48 ` Alexandre Petrescu
2023-12-08 11:54 ` Steven
2023-12-08 12:07 ` Alexandre Petrescu
2023-12-08 12:24 ` Steven
2023-12-08 12:46 ` Alexandre Petrescu
2023-12-08 14:15 ` Alexandre Petrescu
2023-12-11 15:30 ` Alexandre Petrescu
2023-12-12 1:09 ` Steven Honson
2023-12-12 2:29 ` J Pan
2023-12-12 2:43 ` Steven
2023-12-12 10:22 ` Alexandre Petrescu
2023-12-12 10:33 ` Steven
2023-12-12 10:50 ` Sebastian Moeller
2023-12-13 10:33 ` Alexandre Petrescu
2023-12-13 14:37 ` Marc Blanchet
2023-12-13 18:27 ` David Lang [this message]
2023-12-14 13:27 ` Alexandre Petrescu
2023-12-23 21:35 ` J Pan
2024-01-06 15:01 ` Alexandre Petrescu
2024-01-08 10:01 ` [Starlink] starlink topology with tunnels (was: Info on IP country ranges) Alexandre Petrescu
2024-01-08 10:06 ` [Starlink] starlink topology with tunnels Alexandre PETRESCU
2023-12-12 10:52 ` [Starlink] Info on IP country ranges Alexandre Petrescu
2023-12-08 10:28 ` Alexandre Petrescu
2023-12-08 10:31 ` Gert Doering
2023-12-13 20:58 David Fernández
2023-12-13 22:57 ` Marc Blanchet
2023-12-13 22:59 ` Marc Blanchet
2023-12-24 1:29 ` Lukasz Bromirski
2024-01-06 14:59 ` Alexandre Petrescu
2024-01-06 15:06 ` Dave Taht
2024-01-08 10:54 ` Sebastian Moeller
2024-01-08 13:16 ` 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=4rooss86-p114-8qp1-38r8-rn4302n99or4@ynat.uz \
--to=david@lang.hm \
--cc=alexandre.petrescu@gmail.com \
--cc=bufferbloat-lists@steven.honson.au \
--cc=moeller0@gmx.de \
--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