From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id CC5C13B29D for ; Fri, 8 Dec 2023 07:46:23 -0500 (EST) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 3B8CkLEw064292; Fri, 8 Dec 2023 13:46:21 +0100 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id CD38E203623; Fri, 8 Dec 2023 13:46:21 +0100 (CET) Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id BE6FA2034CF; Fri, 8 Dec 2023 13:46:21 +0100 (CET) Received: from [10.8.32.70] (is156570.intra.cea.fr [10.8.32.70]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 3B8CkLZ6008867; Fri, 8 Dec 2023 13:46:21 +0100 Message-ID: <052a8da7-f9a4-47d2-ba80-d1f421f12e0d@gmail.com> Date: Fri, 8 Dec 2023 13:46:21 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: fr To: Steven , Freddie Cash Cc: starlink@lists.bufferbloat.net 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> From: Alexandre Petrescu In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-CEA-Virus: SOPHOS_SAVI_ERROR_OLD_VIRUS_DATA 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: Fri, 08 Dec 2023 12:46:24 -0000 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... True, it would be unusual, but it is practiced. > >> 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. YEs, that latency argument is a good reason. > >> 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. Thanks.  That convinces me it is as you say: the /56 is provided by the starlink DHCPv6-PD server situated in the ground network of starlink somewhere. This makes it for a great tool for many things. Alex > > Cheers, > Steven