From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 34CA43CB41 for ; Mon, 11 Dec 2023 21:43:26 -0500 (EST) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id B86CA3201965; Mon, 11 Dec 2023 21:43:23 -0500 (EST) Received: from imap43 ([10.202.2.93]) by compute3.internal (MEProxy); Mon, 11 Dec 2023 21:43:24 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=honson.au; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1702349003; x=1702435403; bh=tmVP+FJSOROXNI2DfY2MGV389s4dpaxYlat2saVEopQ=; b= jAqxLFOJiem9AqFLVLmMsi3v+6I5/oxF6C0Nk2g1A2Fl7GqTUTF2WgSmecqB05ui SrNPixoeCkjykym+5pVj3XiCZ7C6SkznMkW3JhGD+cifvYHAaqA0E+pKbpKyDHCM w5+Z9siBdska4LOrbK8FSnpX0ADcFuARqOwCix2HIsR76U8gIOiFFNtbC/Dn1O2T njJURzWJfdAcsFGUWH7qNgrf1i7QtV+r5aBf6a8yR5Cox/eTTb5cbmKMV9G+ICgH jpYGfiGERgCab02TWS+HRaZcXPxiBCwGrCKJf3hLHo6YAuUtxJhPgSUGgjNEjXrO NCISSvkYpxuriQVsG8RFiQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1702349003; x= 1702435403; bh=tmVP+FJSOROXNI2DfY2MGV389s4dpaxYlat2saVEopQ=; b=D cakPNKW+fjFHWVzzKcGMV/rCI1ws1fhjekPWSagiK7Z/gQpULsUf2lkCGKx09IAE WNoKfPb3ZHHCo8+5rNMmVKkGmQVANz9jEQYKTqL89B2YgWAXRM5mae751Wd53WA4 Z33WZjAF+ArscbruBXpiiIWIIfCNRfxuwCrl8tELeQ1za4uGzt/6BtIdtScr3Ceo tbXZuTY964/TiQpaouN6rwOWZ7/s5xTRZxfjIhDTrAeGWwR0q5k4VzajdA8Uk5gK TxBHQg4COr/4g6GvLfEQQdcHMjR+uEj+oA7cn1A2ijRlHp0uNS8BvNR6gGUf8Dkk Z4iXrerd+HCUWuTp/57UA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrudelfedghedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvfevufgtgfesthhqredtreerjeenucfhrhhomhepufht vghvvghnuceosghufhhfvghrsghlohgrthdqlhhishhtshesshhtvghvvghnrdhhohhnsh honhdrrghuqeenucggtffrrghtthgvrhhnpefhjedvkedugeekteehheetveehveegtefh ffffvddujeelvdeuveefhfeggeelffenucffohhmrghinhepshhtrghrlhhinhhkrdgtoh hmpdhrvggrughmvgdrihhopdhuvhhitgdrtggrpdhsphgvvgguthgvshhtrdhnvghtpdgs uhhffhgvrhgslhhorghtrdhnvghtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrg hmpehmrghilhhfrhhomhepsghufhhfvghrsghlohgrthdqlhhishhtshesshhtvghvvghn rdhhohhnshhonhdrrghu X-ME-Proxy: Feedback-ID: iaed446c2:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 9BACE2D40087; Mon, 11 Dec 2023 21:43:22 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.9.0-alpha0-1283-g327e3ec917-fm-20231207.002-g327e3ec9 MIME-Version: 1.0 Message-Id: <19c3c701-7c1a-4f04-a35f-bbec3055a54b@app.fastmail.com> In-Reply-To: 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> Date: Tue, 12 Dec 2023 13:43:02 +1100 From: Steven To: "J Pan" 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:43:26 -0000 Thanks for this reference that explicitly states it is IPv6 native. https://support.starlink.com/?topic=3D1192f3ef-2a17-31d9-261a-a59d215629= f4 is another Starlink resource that confirms that a /56 is provided. Th= is one doesn't explicitly mention native, but as mentioned I am confiden= t it is. Cheers, Steven On Tue, 12 Dec 2023, at 1:29 PM, J Pan wrote: > 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.C= A/~pan > > 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 IPv= 6, 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 /5= 6. >> > >> > But to be native IPv6, it would need the IPv6 packets to travel nat= ively >> > (sit directly on the link layer) between home and starlink network.= If >> > these IPv6 packets are encapsulate in IPv4, then there would be a r= isk >> > 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 cl= ient >> > vs from an IPv6-only client. An IPv6-only Windows client can be ma= de by >> > unchecking the IPv4 box in interface Properties window. >> > >> > Ideally, if it is IPv6 native, the latency reported by speedtest.ne= t is >> > approximatively the same on IPv4 vs on IPv6 (sometimes the IPv6 lat= ency >> > is even lower than on IPv4). If the latency reported on IPv6 is hi= gher >> > 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 encapsulati= ng >> > 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 the >> >>> MikroTik router? >> >> That would be quite the unusual setup, and even so would require t= hat I obtain said /56 from elsewhere (such as via a tunnel) to then dele= gate 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 DH= CPv6-PD >> >>> local server config files. >> >> I am confident this is not the case since I configured these route= rs 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 DHCP= v6 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 netw= ork. >> >> Yes, this is the most likely place they are running this, likely t= he 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 allo= cated is also from the same /32 as this DHCPv6 server, with the /32 bein= g 2406:2d40::/32, which you'll note is allocated to Starlink. >> >> >> >> Cheers, >> >> Steven >> _______________________________________________ >> Starlink mailing list >> Starlink@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/starlink