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 40C443CB41 for ; Mon, 11 Dec 2023 20:10:23 -0500 (EST) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id F3CC5320234F; Mon, 11 Dec 2023 20:10:21 -0500 (EST) Received: from imap43 ([10.202.2.93]) by compute3.internal (MEProxy); Mon, 11 Dec 2023 20:10:22 -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=1702343421; x=1702429821; bh=hjySw9S97AJSWvtdzt9PUuyxRgY3X7PZJFWgvkpSFmw=; b= r1L6I/EYdw/h0Ovrr+HXHyC4LzEDQgequkdpQQENwU2z5B/PsdxlOw7LO66o5F1d U3WflxBKdo4LKl8VbTxgSIi5kzv+b6LpVspn1gzgltYHlFpImkdB3LVC86hSsxwf Us2ThhPZ6u26C+LKwwVrt0JmtbiG6BtK15jRYvluvzWw11ScTsRU0R7UB/whMyKM Ji+zFtC1GzEBWS6WJH6n1oOCQiYbNBmCb2E1zfAYqrob7yzOTIjnCNtnmdRHibMc +7J0L7c4jJwN3uDBWVqtl1q1UuluQK75Amxad1IdMnva9YSYTQN6cRMZw8qDXbBa mPoNJi+pTjkJrfjLCr9KmQ== 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=1702343421; x= 1702429821; bh=hjySw9S97AJSWvtdzt9PUuyxRgY3X7PZJFWgvkpSFmw=; b=D 910LrmVbYGy5bAg6NRINQeV5lng9tTzcWO+zWHNGxWG1Z+JTWzdIrOk99207E0SQ GemattXlHBKHlbWqjo41XgC3zAQ9vCkCLhKta0sMrS8O7cwjZy76biUCIOGZvCRl K1JUjv/eU8EJ3XTbekVe+onHRQuxtcy3Be8NInrgCvFpKxdLuea1UojPNZ70XiMD ItkiDdoYcM91PFlQdt+9upP/W4gXuswr9BkAlkCnlgsPLGQ34S/DrwdrF4xfm0tO 1DabU1D8704HtDhLNN74HLAAqEXYhghoH3KhzH92eNnoOkwMZomeSkxdjulVG0Or 6wAYalu6yVz3oiWsdgutw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrudelfedgfedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvfevufgtgfesthhqredtreerjeenucfhrhhomhepfdfu thgvvhgvnhcujfhonhhsohhnfdcuoegsuhhffhgvrhgslhhorghtqdhlihhsthhssehsth gvvhgvnhdrhhhonhhsohhnrdgruheqnecuggftrfgrthhtvghrnhepfeetvdefleetgeei veejleeigfelheeihfekhfejheeiudehvdefgfdtvdetleeknecuffhomhgrihhnpehsph gvvgguthgvshhtrdhnvghtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehm rghilhhfrhhomhepsghufhhfvghrsghlohgrthdqlhhishhtshesshhtvghvvghnrdhhoh hnshhonhdrrghu X-ME-Proxy: Feedback-ID: iaed446c2:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 367E42D4007D; Mon, 11 Dec 2023 20:10:21 -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: <21b2df7e-23c6-4c84-980f-635f41483c29@app.fastmail.com> In-Reply-To: <4d0cd8c6-9de7-4976-8d46-ef159ea06c58@gmail.com> 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> Date: Tue, 12 Dec 2023 12:09:58 +1100 From: "Steven Honson" To: "Alexandre Petrescu" Cc: 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 01:10:23 -0000 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=20 > 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 native= ly=20 > (sit directly on the link layer) between home and starlink network.=C2= =A0 If=20 > these IPv6 packets are encapsulate in IPv4, then there would be a risk=20 > of additional latency compared to v4. > > A possible way to find out whether it's IPv6 native (and hence no=20 > additional latency) is to browse speedtest.net from an IPv4-only clien= t=20 > vs from an IPv6-only client.=C2=A0 An IPv6-only Windows client can be = made by=20 > unchecking the IPv4 box in interface Properties window. > > Ideally, if it is IPv6 native, the latency reported by speedtest.net i= s=20 > approximatively the same on IPv4 vs on IPv6 (sometimes the IPv6 latenc= y=20 > is even lower than on IPv4).=C2=A0 If the latency reported on IPv6 is = higher=20 > than on IPv4 it could be for many reasons, and one of them could be th= at=20 > IPv6 is not native, but encapsulated in IPv4.=C2=A0 The IPv4 encapsula= ting=20 > endpoint could be on Dishy. > > Alex > > Le 08/12/2023 =C3=A0 13:24, Steven a =C3=A9crit=C2=A0: >> 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 delegat= e 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 DHCPv= 6-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 Gro= und->Space->Ground latency I'd expect. >> >>> It could also be that the DHCPv6-PD server is run on the starlink gr= ound >>> 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 allocat= ed is also from the same /32 as this DHCPv6 server, with the /32 being 2= 406:2d40::/32, which you'll note is allocated to Starlink. >> >> Cheers, >> Steven