From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: Steven <bufferbloat-lists@steven.honson.au>,
Freddie Cash <fjwcash@gmail.com>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Info on IP country ranges
Date: Mon, 11 Dec 2023 16:30:19 +0100 [thread overview]
Message-ID: <4d0cd8c6-9de7-4976-8d46-ef159ea06c58@gmail.com> (raw)
In-Reply-To: <dd928866-19de-44dc-a464-4c8c43da1979@app.fastmail.com>
Steven,
Thanks for the clarifications. It is indeed very advantageous to use
DHCPv6-PD from a Client in home to starlink Server, and obtain a /56.
But to be native IPv6, it would need the IPv6 packets to travel natively
(sit directly on the link layer) between home and starlink network. If
these IPv6 packets are encapsulate in IPv4, then there would be a risk
of additional latency compared to v4.
A possible way to find out whether it's IPv6 native (and hence no
additional latency) is to browse speedtest.net from an IPv4-only client
vs from an IPv6-only client. An IPv6-only Windows client can be made by
unchecking the IPv4 box in interface Properties window.
Ideally, if it is IPv6 native, the latency reported by speedtest.net is
approximatively the same on IPv4 vs on IPv6 (sometimes the IPv6 latency
is even lower than on IPv4). If the latency reported on IPv6 is higher
than on IPv4 it could be for many reasons, and one of them could be that
IPv6 is not native, but encapsulated in IPv4. The IPv4 encapsulating
endpoint could be on Dishy.
Alex
Le 08/12/2023 à 13:24, Steven a écrit :
> Alexandre,
>
>> Are you sure the DHCPv6-PD server is in Starlink network and not on the
>> MikroTik router?
> That would be quite the unusual setup, and even so would require that I obtain said /56 from elsewhere (such as via a tunnel) to then delegate back to myself...
>
>> It could be that the MikroTik router runs tunnelbroker, obtains a /56
>> from HE, splits that /56 into multiple /64s and puts it on the DHCPv6-PD
>> local server config files.
> I am confident this is not the case since I configured these routers from scratch.
>
>> It could also be that the DHCPv6-PD server is run on the Dishy.
> It is unlikely that it is on the Dishy, as the latency to the DHCPv6 servers IP address, as well as the first IP hop, indicates the usual Ground->Space->Ground latency I'd expect.
>
>> It could also be that the DHCPv6-PD server is run on the starlink ground
>> network: maybe on the teleport, maybe deeper on the starlink network.
> Yes, this is the most likely place they are running this, likely the PoP you are being routed through.
>
>> Do you know the IPv6 address of your DHCPv6-PD Server?
> The DHCPv6 server address is a Starlink IPv6 address, the same one as my default gateway (`2406:2d40:xxx:xxx::1`). The /56 I am being allocated is also from the same /32 as this DHCPv6 server, with the /32 being 2406:2d40::/32, which you'll note is allocated to Starlink.
>
> Cheers,
> Steven
next prev parent reply other threads:[~2023-12-11 15:30 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 [this message]
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 ` [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=4d0cd8c6-9de7-4976-8d46-ef159ea06c58@gmail.com \
--to=alexandre.petrescu@gmail.com \
--cc=bufferbloat-lists@steven.honson.au \
--cc=fjwcash@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