From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw1-f176.google.com (mail-yw1-f176.google.com [209.85.128.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 76A6E3CB41 for ; Mon, 11 Dec 2023 21:29:28 -0500 (EST) Received: by mail-yw1-f176.google.com with SMTP id 00721157ae682-5d74186170fso45925167b3.3 for ; Mon, 11 Dec 2023 18:29:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702348168; x=1702952968; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=cc/KYh6bTZ5yPnJWq4xbtM6hsJlIJNLOLGpeLPf5yc4=; b=jzck3jK58V++lq8NinDZyZl8LZ/VX41Yw7E0W0rh8We1CIOgoWWMhdltblNX8ZOKip B3ogfOKWYNxdiNHblrztu5zlJH+xCHvfpMvpmIXheOkV/vKGxqGmlZUR6j9cCnuCHeWB G8zhu42nlYceKCpPcGaUhM1JjgxNCKx2J2+9TjZAllu+IJ/YSrZIAyNH9VZG22LFfruD 5sMGlwzzdc9AeIz6txD1D5rgctSI053/0Ewyue3tBHEFbJLPDBGuBhfbiGCYJgy6xTyN mv5tcRDb0UPH6voSMTp/vsOfeYhUWQhB5HPBP/QJvIP106esU1xsCZYPPsvOkyUPvdXH L4KQ== X-Gm-Message-State: AOJu0YyJUtg/HG6GHSfCudWpH3a/bw1bM9vFG4eFJT5TpHTnqcf6Jgpj rOHm+QdBQ5rODEDFEugbnQvw8YvBnLG1yyNuUx8= X-Google-Smtp-Source: AGHT+IHCLmPoydzJkdMcjgukfhMnpPZCWlpx6otmugXdOBY8V6HwAeeUs/QxUVnsaJmn1LoesWweGbQVoQQpb07VVqQ= X-Received: by 2002:a0d:d656:0:b0:5d7:501b:4da3 with SMTP id y83-20020a0dd656000000b005d7501b4da3mr4329128ywd.51.1702348167647; Mon, 11 Dec 2023 18:29:27 -0800 (PST) MIME-Version: 1.0 References: <361ee9d0d01da491a6e2b132317d170b@ausics.net> <75790520d6c8d35beb7248f5f5dff952@ausics.net> <924492fc-6ce4-4e62-82d9-c8f0b50ee96d@gmail.com> <8a807397-edef-4dcc-bfa6-f9c1598cbc77@gmail.com> <69da68cf-8746-45f8-9537-8fd8252de115@gmail.com> <7a20ea4f-4f16-4584-9f53-1ee3c72afd6f@app.fastmail.com> <26abce66-300f-405e-ad18-cc32695580fa@gmail.com> <4d0cd8c6-9de7-4976-8d46-ef159ea06c58@gmail.com> <21b2df7e-23c6-4c84-980f-635f41483c29@app.fastmail.com> In-Reply-To: <21b2df7e-23c6-4c84-980f-635f41483c29@app.fastmail.com> From: J Pan Date: Mon, 11 Dec 2023 18:29:15 -0800 Message-ID: To: Steven Honson Cc: Alexandre Petrescu , starlink@lists.bufferbloat.net Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [Starlink] Info on IP country ranges X-BeenThere: starlink@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Starlink has bufferbloat. Bad." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Dec 2023 02:29:28 -0000 yes. https://starlink-enterprise-guide.readme.io/docs/ip-addresses "Starlink is IPv6 native network. Using IPv6 is more flexible and future-proof." starlink has greatly improved tech docs -- J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pa= n On Mon, Dec 11, 2023 at 5:10=E2=80=AFPM Steven Honson via Starlink wrote: > > Hi Alex, > > As an experienced network engineer with extensive experience with IPv6, I= 'm confident this is native IPv6. > > Cheers, > Steven > > On Tue, 12 Dec 2023, at 2:30 AM, Alexandre Petrescu wrote: > > 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 nativel= y > > (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 b= y > > 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 tha= t > > IPv6 is not native, but encapsulated in IPv4. The IPv4 encapsulating > > endpoint could be on Dishy. > > > > Alex > > > > Le 08/12/2023 =C3=A0 13:24, Steven a =C3=A9crit : > >> Alexandre, > >> > >>> Are you sure the DHCPv6-PD server is in Starlink network and not on t= he > >>> 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 ba= ck 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 f= rom 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 s= ervers 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 gro= und > >>> network: maybe on the teleport, maybe deeper on the starlink network. > >> Yes, this is the most likely place they are running this, likely the P= oP 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 i= s also from the same /32 as this DHCPv6 server, with the /32 being 2406:2d4= 0::/32, which you'll note is allocated to Starlink. > >> > >> Cheers, > >> Steven > _______________________________________________ > Starlink mailing list > Starlink@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/starlink