From: Alexandre PETRESCU <alexandre.petrescu@cea.fr>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] starlink topology with tunnels
Date: Mon, 8 Jan 2024 11:06:48 +0100 [thread overview]
Message-ID: <d0f73737-6fdb-4114-a3c3-e3f4e60d6b09@cea.fr> (raw)
In-Reply-To: <38158e52-e494-4acc-8108-60e4153f225e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1339 bytes --]
[with the attachment, sorry]
The figure of starlink topology with tunnels is in the attachment of
this email. It comes from
https://www.reddit.com/r/StarlinkEngineering/comments/17w3sey/a_better_illustration_about_starlink_user/
The original poster's text about the figure is: "a better illustration
about starlink user terminal (ut), community gateway (cg), ground
station (gs), gateway (gw), carrier-grade network address translator
(cgnat), point-of-presence (pop), etc ".
It is a user opinion.
Alex
Le 06/01/2024 à 16:01, Alexandre Petrescu via Starlink a écrit :
>
>
> Le 23/12/2023 à 22:35, J Pan a écrit :
>> starlink uses tunnels a lot
>> https://www.reddit.com/r/StarlinkEngineering/comments/17w3sey/a_better_illustration_about_starlink_user/
>>
>> . starlink assigned ip addresses are pop-specific
>> --
>> J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA,
>> Web.UVic.CA/~pan
>
> That is a good point. Thank you for the figure!
>
> I will discuss it separately, if appropriate.
>
> 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: 7r3tjmjntk0c1.png --]
[-- Type: image/png, Size: 15980 bytes --]
next prev parent reply other threads:[~2024-01-08 10:06 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 0:15 [Starlink] Info on IP country ranges 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
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 ` Alexandre PETRESCU [this message]
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
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=d0f73737-6fdb-4114-a3c3-e3f4e60d6b09@cea.fr \
--to=alexandre.petrescu@cea.fr \
--cc=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