From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yb1-f175.google.com (mail-yb1-f175.google.com [209.85.219.175]) (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 4EE303CB39 for ; Thu, 7 Dec 2023 13:08:02 -0500 (EST) Received: by mail-yb1-f175.google.com with SMTP id 3f1490d57ef6-db3a09e96daso1450411276.3 for ; Thu, 07 Dec 2023 10:08:02 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701972482; x=1702577282; 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=qRd75BMOZKTP/MS7oKUASLHicPusZESwLO+nUBT+GOE=; b=vnAfKeIUPNY0bfuHNTrKRkQb0wX/9xf7wsMdKXwuveHtRASnApKFuVjIpSDUY61VQL X8yw9RlertTx/81YvnbF1dco4iVT3qNhV6e34KAp+L4qtE+m1gypITlHE2Br/h1/AfY1 5RyBWfdJsMA8WS0Wg3XF7NV6+Gyb5a29jo3t+5pL7m+hcHJYiML8x36WrOvwpStoLTI5 njenrvWBz1Rcn0XKsfatTLx2f4zu7lDBQginiLhR+lMfILGXG//9lw1DaxuUssGGy63V b/33Z9N54K1M7sScvYNyAjklOzDkFXTvB2Ro/Rr9T7NpiroNjN1x1q4y7VJqpkuEAd02 T9Ag== X-Gm-Message-State: AOJu0YwJjBhOwOE0ttcidhZnLTfKLroDDsaOhVL1+hOd4+xPujUArvkr WH9pv6wFNz0Sish1yVoF+NWOArXemFDTWsZ6EgZOjL2i X-Google-Smtp-Source: AGHT+IEbhtUB0kXqPEBA6xwMb71EPS9CU91GOtB3eRuBgZIOtU382OMhP3B7cknm2uETZmNyt58eVTEU2YA5C9dy1qc= X-Received: by 2002:a05:6902:4d3:b0:db5:43a6:3cfc with SMTP id v19-20020a05690204d300b00db543a63cfcmr2753846ybs.35.1701972481593; Thu, 07 Dec 2023 10:08:01 -0800 (PST) MIME-Version: 1.0 References: <361ee9d0d01da491a6e2b132317d170b@ausics.net> <75790520d6c8d35beb7248f5f5dff952@ausics.net> <924492fc-6ce4-4e62-82d9-c8f0b50ee96d@gmail.com> In-Reply-To: <924492fc-6ce4-4e62-82d9-c8f0b50ee96d@gmail.com> From: J Pan Date: Thu, 7 Dec 2023 10:07:50 -0800 Message-ID: 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: Thu, 07 Dec 2023 18:08:02 -0000 yes, user router gets a public ipv6 address block from starlink to distribute in its local network. starlink network is ipv6 native (although www.starlink.com is not accessible by ipv6 yet, while geoip.starlinkisp.net is----the classic fight between noc, nic and nmc---network measurement center people ;-) on the other hand, starlink-provided user router does not support configuration to allow incoming connections. users can bypass it and use their more configurable router, but still have to use the stock one for power-over-ethernet for gen-2 dishes ;-) -- J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pa= n On Thu, Dec 7, 2023 at 3:55=E2=80=AFAM Alexandre Petrescu via Starlink wrote: > > > Le 04/12/2023 =C3=A0 19:17, J Pan via Starlink a =C3=A9crit : > > yes, starlink does respond to its customers' complaints, although > > sometimes slowly. its ipv4 address acquisition is scattered around as > > a latecomer to the isp world, and as a global local isp, it's more > > 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 can 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. That is easy to find out by just looking > at the packets. This would tell whether a NAT can be avoided at home, > and hence more apps made possible. > > IT would also be good to know whether the claimed IPv6 access on dishy > is via a tunnel (IPv6 in IPv6, or IPv6 in IPv4) or it is 'native' (no > tunnel). That will tell many things about additional latency that might > be brought in by IPv6. (we'd want less latency, not more). > > After that, one can look more at promoting IPv6. 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 enough 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.C= A/~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, s= o 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 us= er 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.1= 80 ms ae-1.r20.frnkge13.de.bb.gin.ntt.net (129.250.7.35) 280.523 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 2= 78.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 only allow access by IP, I'm hoping someone here knows if they are ful= l of it, or does starlink really assign addresses from anywhere? That one h= ardly makes sense for user experience, or maybe starlink has so few users i= n 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