From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 58B6F3CB39 for ; Fri, 8 Dec 2023 03:41:03 -0500 (EST) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 1A8103200B26; Fri, 8 Dec 2023 03:41:02 -0500 (EST) Received: from imap43 ([10.202.2.93]) by compute3.internal (MEProxy); Fri, 08 Dec 2023 03:41:02 -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:sender:subject:subject:to:to; s=fm1; t= 1702024861; x=1702111261; bh=XbFmXPvulWFFg0vAIfSj847D2O+52KjUWOW nYRGRrUE=; b=kDTQ7ni7cLn9sJrtiNB/NPvwsUEbIjhDtCEJe7wzSUpI7JaWDtI XBp1DVVz1+QzmNLQ1j9f6S2RXc+/P2l5mqp0b9Kg6fRcrP28j7MZkCkQq69V1jLb 7dl1GDZiEx1Xy6u8m4jY7jHRKhUnlmg9iAtDyGr3d2jvvGD6Gsno0OlejULlKWIM mpOGP+lLRo+K4RpTJBx5NMBUZw+CGCFGdCll+Ur23O60awEv9+NgUDD/phFfzU10 oTmhGhc47YTqCxMEnqiqiO+LIvIWM2cwYWxjiY0nsWFu8lXGnz3CZrNS/IfdRDFw R+0JXMRYPRDUlVIc7nOi0CSfTJgAvr/fXFw== 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:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1702024861; x=1702111261; bh=XbFmXPvulWFFg0vAIfSj847D2O+52KjUWOW nYRGRrUE=; b=jQe/QOHxX/cW89EBZkWyYjG9IU7MTpoDnmh20F4tUg/NmZLKflq lTyxpsNs8nnpJWtFBPppLPwj/u6glLlsBmkSUXJyMl6ap6M05DP5P9DXwqC7cUnL IKgBYMYHUp3xf8dHqyQDUf3D2JJo3taH+FNR7LlwGHsOH2FGdSWj1unp7pklmlUv aTswEooxWPbZY+exPptsrO3irGq/PhFDoU99q9/4J/RNwBQpsBORR28wJ4sRiauR x0xUIV4Rb7WB7OS+7D+ZsKSzlaui/KjqLcEZ2jREa8tejAlQkHdDjXkUJ4XIXWwN r+Ke2stwUvaOXWqnyxkkJ/3q4jCsiOdGMLQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrudekhedgieekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvfevufgtgfesthhqredtreerjeenucfhrhhomhepufht vghvvghnuceosghufhhfvghrsghlohgrthdqlhhishhtshesshhtvghvvghnrdhhohhnsh honhdrrghuqeenucggtffrrghtthgvrhhnpeetleeuueeljedujeehieeutdelhefghfdv gefhhfegkeevtdfftdfhtdffueffleenucffohhmrghinhepuhhvihgtrdgtrgdpshhtrg hrlhhinhhkihhsphdrnhgvthdpuggvrdgssgdpnhhtthdrnhgvthdpsghufhhfvghrsghl ohgrthdrnhgvthenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpegsuhhffhgvrhgslhhorghtqdhlihhsthhssehsthgvvhgvnhdrhhhonhhsohhn rdgruh X-ME-Proxy: Feedback-ID: iaed446c2:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 4F4B92D40074; Fri, 8 Dec 2023 03:41:01 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.9.0-alpha0-1178-geeaf0069a7-fm-20231114.001-geeaf0069 MIME-Version: 1.0 Message-Id: In-Reply-To: <8a807397-edef-4dcc-bfa6-f9c1598cbc77@gmail.com> References: <361ee9d0d01da491a6e2b132317d170b@ausics.net> <75790520d6c8d35beb7248f5f5dff952@ausics.net> <924492fc-6ce4-4e62-82d9-c8f0b50ee96d@gmail.com> <8a807397-edef-4dcc-bfa6-f9c1598cbc77@gmail.com> Date: Fri, 08 Dec 2023 19:40:41 +1100 From: Steven To: "Alexandre Petrescu" , "Freddie Cash" 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: Fri, 08 Dec 2023 08:41:03 -0000 You do indeed get a /56, so are able to assign unique /64s to each of yo= ur networks. Your router obtains an address using SLAAC for your WAN interface from a= /64 (not sure if this /64 is unique to each customer or shared). You can then request a /56 using DHCP-PD (separate to the /64 used on th= e WAN interface). Cheers, Steven On Fri, 8 Dec 2023, at 7:30 PM, Alexandre Petrescu via Starlink wrote: > Le 08/12/2023 =C3=A0 06:57, Freddie Cash a =C3=A9crit=C2=A0: >> Dishy gets a /64 > > IF Dishy gets a /64 from the starlink operator then I am afraid one ca= nt=20 > make subnets in home, because each other subnet needs a distinct /64. > > >> and I've tested DHCPv6 on both my Firewalla and my USG. They do prefi= x=20 >> delegation to distribute that as a /56 locally. > > I am afraid it is not possible to make a /56 out of a /64 (the inverse=20 > is true). > > Alex > >> >> No NAT required for IPv6 (incoming or outgoing) connections. And ther= e=20 >> doesn't appear to be any restrictions on IPv6 traffic. >> >> This is with the round Dishy. >> >> Cheers, >> Freddie >> >> Typos due to smartphone keyboard. >> >> On Thu, Dec 7, 2023, 3:54 a.m. Alexandre Petrescu via Starlink=20 >> wrote: >> >> >> Le 04/12/2023 =C3=A0 19:17, J Pan via Starlink a =C3=A9crit=C2=A0: >> > yes, starlink does respond to its customers' complaints, althou= gh >> > sometimes slowly. its ipv4 address acquisition is scattered >> around as >> > a latecomer to the isp world, and as a global local isp, it's m= ore >> > troublesome. ip packets have to be tunneled back to its home pop >> where >> > nat and other functions happen, sometimes around the world, >> causing a >> > much higher minimum rtt fluctuation in 15-second handover >> > intervals---bad for network protocols and applications. ipv6 ca= n do >> > better but currently follows the same route as ipv4---an >> incentive to >> > promote ipv6 ;-) >> >> Excellent incentive! >> >> It would be good to know whether the dishy router obtains a /56 or >> a /64 >> prefix from the starlink ISP.=C2=A0 That is easy to find out by j= ust >> looking >> at the packets.=C2=A0 This would tell whether a NAT can be avoide= d at >> home, >> and hence more apps made possible. >> >> IT would also be good to=C2=A0 know whether the claimed IPv6 acce= ss on >> dishy >> is via a tunnel (IPv6 in IPv6, or IPv6 in IPv4) or it is 'native'= (no >> tunnel).=C2=A0 That will tell many things about additional latenc= y that >> might >> be brought in by IPv6.=C2=A0 (we'd want less latency, not more). >> >> After that, one can look more at promoting IPv6.=C2=A0 Otherwise,= IPv6 >> might >> still look as a hurdle, an obstacle, additional work that is too >> little >> necessary, or might even be worse than IPv4. >> >> Alex >> >> > -- >> > J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, >> Web.UVic.CA/~pan >> > >> > On Mon, Dec 4, 2023 at 4:04=E2=80=AFAM Noel Butler >> wrote: >> >> Thanks, it seems they are trying it on then :) >> >> >> >> On 04/12/2023 10:44, J Pan wrote: >> >> >> >> starlink advertises its customer ip address location at >> >> http://geoip.starlinkisp.net (not always updated but good enou= gh in >> >> most cases and traceroute can confirm to some extent as well) >> >> -- >> >> J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, >> Web.UVic.CA/~pan >> >> >> >> On Sun, Dec 3, 2023 at 4:15=E2=80=AFPM Noel Butler via Starlink >> >> wrote: >> >> >> >> >> >> I run an open access usenet server, but only for those within >> my CC, so access is by IP based on our CC allocations from APNIC. >> >> >> >> Because IPv4 exhaustion this changes sometimes with buying >> allocations from other regions, and if they get denied access I >> encourage them to let us know so we can keep ACL's updated, I've >> had a request from a starlink user who claims they are here, but >> traceroute shows them in .DE >> >> >> >> tracing some 217.foo.ad.dr >> >> >> >> ... >> >> 9 ae-6.r21.frnkge13.de.bb.gin.ntt.net >> (129.250.3.183) >> 290.223 ms 290.180 ms ae-1.r20.frnkge13.de.bb.gin.ntt.net >> (129.250.7.35) 280.5= 23 ms >> >> 10 ae-1.a03.frnkge13.de.bb.gin.ntt.net >> (129.250.3.152) >> 290.109 ms 289.667 ms 292.864 ms >> >> 11 ae-0.spacex.frnkge13.de.bb.gin.ntt.net >> (213.198.72.19) >> 279.611 ms 278.840 ms 279.592 ms >> >> 12 undefined.hostname.localhost (206.224.65.189) 280.127 ms >> 278.506 ms 284.265 ms >> >> 13 undefined.hostname.localhost (206.224.65.209) 284.198 ms >> undefined.hostname.localhost (206.224.65.201) 274.663 ms 273.073 = ms >> >> 14 * * * >> >> >> >> >> >> As it is our policy to not collect any user info or issue >> user/pass's and=C2=A0 only allow access by IP, I'm hoping someone= here >> knows if they are full of it, or does starlink really assign >> addresses from anywhere? That one hardly makes sense for user >> experience, or maybe starlink has so few users in this country >> they haven't bothered changing anything yet? >> >> >> >> -- >> >> >> >> Regards, >> >> Noel Butler >> >> >> >> >> >> _______________________________________________ >> >> Starlink mailing list >> >> Starlink@lists.bufferbloat.net >> >> https://lists.bufferbloat.net/listinfo/starlink >> >> >> >> >> >> -- >> >> >> >> Regards, >> >> Noel Butler >> >> >> >> >> > _______________________________________________ >> > Starlink mailing list >> > Starlink@lists.bufferbloat.net >> > https://lists.bufferbloat.net/listinfo/starlink >> _______________________________________________ >> Starlink mailing list >> Starlink@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/starlink >> > _______________________________________________ > Starlink mailing list > Starlink@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/starlink