From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) (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 8C4B33B29D for ; Fri, 8 Dec 2023 10:28:01 -0500 (EST) Received: by mail-yb1-xb2a.google.com with SMTP id 3f1490d57ef6-db537948ea0so2332164276.2 for ; Fri, 08 Dec 2023 07:28:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1702049281; x=1702654081; darn=lists.bufferbloat.net; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=uMe++SGooKqEX5U7WPR5FHWQFJrvMLtqRxAW6qcqWcA=; b=DduvN6sUJo3gBorL88VLyoJeS8/0KOFQ9OycWp/Pf9SIljbpNq7FBnZpzSzYswUPf0 qS6ynInIuURhoxjw55wreCWjwk6YSSHeB1VVA0TulNykIKn/+XjVh8U4nm1ax/googKQ aPo1HLhynrmpmApUTOQTTkarJsNqdYD3mydfKmLXnM9wf6+lVx7KWh5R8mFwniu6/k9f 4WbKDxMTT6Pg+Y9xWzAsSvdArsPlOL/pBlep9mSqFG7aREK7OtJcW/9dPjU/0LGCFYIf 0IYCJiiP3lG4awd0xxgJTxRuEtdMj5dFqgi1YQD/esqVoujX6QtSP+qQ7K/Nct1AvszW 6CrA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702049281; x=1702654081; h=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=uMe++SGooKqEX5U7WPR5FHWQFJrvMLtqRxAW6qcqWcA=; b=PSBt0RE4OASa7kUPPwu0d9rZjfw/NFKEppTWjY+XGS5GyukgAGkwugjDd8RfuQsIpg PUx2dS2lkj6vWrkZ5q8kNgV+LYFGDPbMSYsOAwPuDZMX8hSRjcTnx/I2c4+AVRNBVq// EByxpgBVw+MGV+7XMjzQmq133PYJzF4zYZyByERIMhT5WUZQpiBT11/1Ya33ziERbcu+ r3mFOpoBaMbGJLM/b4Yw5OWKNs/M/g9jC4KIVdRdh2Qd71ukvkQq9G8DHOBCYW6MSpmx sFEGbr8Or0N923Xm6X0rnAFsTtpsAuG6EiBquxNWn9mh8qowgkY8O3EL1NUOgJx5+YaE 3c7g== X-Gm-Message-State: AOJu0YxDKwVGAuAYJro4pj0BPi9UoPm3xDVDbrHzW6kUbhG4dlyma1ll KJ0JwOE3G3us7gT3WxLs4WZbQvxloqgqjiTyieQ= X-Google-Smtp-Source: AGHT+IHsdoYKOOw8ZprwzqsZvRZ5lW5xtjrPxsSWGQpeVPBR3vUuvkXj6IebmalkiAhCiMZ8Ke+NMvOSLJn0zPwM28w= X-Received: by 2002:a5b:ec4:0:b0:db9:60ae:efc1 with SMTP id a4-20020a5b0ec4000000b00db960aeefc1mr93878ybs.85.1702049280630; Fri, 08 Dec 2023 07:28:00 -0800 (PST) MIME-Version: 1.0 References: <361ee9d0d01da491a6e2b132317d170b@ausics.net> <75790520d6c8d35beb7248f5f5dff952@ausics.net> <924492fc-6ce4-4e62-82d9-c8f0b50ee96d@gmail.com> <8a807397-edef-4dcc-bfa6-f9c1598cbc77@gmail.com> In-Reply-To: From: Freddie Cash Date: Fri, 8 Dec 2023 07:27:49 -0800 Message-ID: To: Alexandre Petrescu Cc: starlink@lists.bufferbloat.net Content-Type: multipart/alternative; boundary="000000000000c3236d060c013aec" 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 15:28:01 -0000 --000000000000c3236d060c013aec Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sorry, you're right, I got that wrong. Was going from memory. Checking the Firewalla, it's a /64 on both the WAN (via DHCPv6) and LAN interfaces (via prefix delegation). Cheers, Freddie Typos due to smartphone keyboard. On Fri, Dec 8, 2023, 12:37 a.m. Alexandre Petrescu via Starlink < starlink@lists.bufferbloat.net> wrote: > > Le 08/12/2023 =C3=A0 09:30, Alexandre Petrescu via Starlink a =C3=A9crit = : > > > > Le 08/12/2023 =C3=A0 06:57, Freddie Cash a =C3=A9crit : > >> Dishy gets a /64 > > > > IF Dishy gets a /64 from the starlink operator then I am afraid one > > cant 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 > >> prefix 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 > > is true). > > For clarification: there could be a way to make a /56 out of a /128 out > of that /64. The way to do that is to do tunnelling - a third party > router would use a tunnelling gateway outside the starlink domain. But > tunnelling means addition of latency. That would not be an incentive. > > Alex > > > > > Alex > > > >> > >> No NAT required for IPv6 (incoming or outgoing) connections. And > >> there 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 > >> wrote: > >> > >> > >> Le 04/12/2023 =C3=A0 19:17, J Pan via Starlink a =C3=A9crit : > >> > yes, starlink does respond to its customers' complaints, althoug= h > >> > sometimes slowly. its ipv4 address acquisition is scattered > >> around as > >> > a latecomer to the isp world, and as a global local isp, it's mo= re > >> > 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.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.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 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 m= s > >> >> 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 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 > _______________________________________________ > Starlink mailing list > Starlink@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/starlink > --000000000000c3236d060c013aec Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Sorry, you're right, I got that wro= ng. Was going from memory.

Che= cking the Firewalla, it's a /64 on both the WAN (via DHCPv6) and LAN in= terfaces (via prefix delegation).

Cheers,
Freddie

Typos due to smartphone keyboa= rd.

On Fri, Dec 8, 2023, 12:37 a.m. Alexandre Petrescu via Star= link <starlink@lists.bufferbloat.net> wrote:

Le 08/12/2023 =C3=A0 09:30, Alexandre Petrescu via Starlink a =C3=A9crit=C2= =A0:
>
> 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 > cant 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 d= o
>> prefix 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=
> is true).

For clarification: there could be a way to make a /56 out of a /128 out of that /64.=C2=A0 The way to do that is to do tunnelling - a third party <= br> router would use a tunnelling gateway outside the starlink domain.=C2=A0 Bu= t
tunnelling means addition of latency.=C2=A0 That would not be an incentive.=

Alex

>
> Alex
>
>>
>> No NAT required for IPv6 (incoming or outgoing) connections. And <= br> >> there 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 >> <starlink@lists.bufferbloat.net> = wrote:
>>
>>
>> =C2=A0=C2=A0=C2=A0 Le 04/12/2023 =C3=A0 19:17, J Pan via Starlink = a =C3=A9crit=C2=A0:
>> =C2=A0=C2=A0=C2=A0 > yes, starlink does respond to its customer= s' complaints, although
>> =C2=A0=C2=A0=C2=A0 > sometimes slowly. its ipv4 address acquisi= tion is scattered
>> =C2=A0=C2=A0=C2=A0 around as
>> =C2=A0=C2=A0=C2=A0 > a latecomer to the isp world, and as a glo= bal local isp, it's more
>> =C2=A0=C2=A0=C2=A0 > troublesome. ip packets have to be tunnele= d back to its home pop
>> =C2=A0=C2=A0=C2=A0 where
>> =C2=A0=C2=A0=C2=A0 > nat and other functions happen, sometimes = around the world,
>> =C2=A0=C2=A0=C2=A0 causing a
>> =C2=A0=C2=A0=C2=A0 > much higher minimum rtt fluctuation in 15-= second handover
>> =C2=A0=C2=A0=C2=A0 > intervals---bad for network protocols and = applications. ipv6
>> can do
>> =C2=A0=C2=A0=C2=A0 > better but currently follows the same rout= e as ipv4---an
>> =C2=A0=C2=A0=C2=A0 incentive to
>> =C2=A0=C2=A0=C2=A0 > promote ipv6 ;-)
>>
>> =C2=A0=C2=A0=C2=A0 Excellent incentive!
>>
>> =C2=A0=C2=A0=C2=A0 It would be good to know whether the dishy rout= er obtains a /56 or
>> =C2=A0=C2=A0=C2=A0 a /64
>> =C2=A0=C2=A0=C2=A0 prefix from the starlink ISP.=C2=A0 That is eas= y to find out by just
>> =C2=A0=C2=A0=C2=A0 looking
>> =C2=A0=C2=A0=C2=A0 at the packets.=C2=A0 This would tell whether a= NAT can be avoided at
>> =C2=A0=C2=A0=C2=A0 home,
>> =C2=A0=C2=A0=C2=A0 and hence more apps made possible.
>>
>> =C2=A0=C2=A0=C2=A0 IT would also be good to=C2=A0 know whether the= claimed IPv6 access on
>> =C2=A0=C2=A0=C2=A0 dishy
>> =C2=A0=C2=A0=C2=A0 is via a tunnel (IPv6 in IPv6, or IPv6 in IPv4)= or it is 'native'
>> (no
>> =C2=A0=C2=A0=C2=A0 tunnel).=C2=A0 That will tell many things about= additional latency that
>> =C2=A0=C2=A0=C2=A0 might
>> =C2=A0=C2=A0=C2=A0 be brought in by IPv6.=C2=A0 (we'd want les= s latency, not more).
>>
>> =C2=A0=C2=A0=C2=A0 After that, one can look more at promoting IPv6= .=C2=A0 Otherwise, IPv6
>> =C2=A0=C2=A0=C2=A0 might
>> =C2=A0=C2=A0=C2=A0 still look as a hurdle, an obstacle, additional= work that is too
>> =C2=A0=C2=A0=C2=A0 little
>> =C2=A0=C2=A0=C2=A0 necessary, or might even be worse than IPv4. >>
>> =C2=A0=C2=A0=C2=A0 Alex
>>
>> =C2=A0=C2=A0=C2=A0 > --
>> =C2=A0=C2=A0=C2=A0 > J Pan, UVic CSc, ECS566, 250-472-5796 (NO = VM), Pan@UVic.CA,
>> =C2=A0=C2=A0=C2=A0 Web.UVic.CA/~pan <http://Web.UVic.CA/~pan>
>> =C2=A0=C2=A0=C2=A0 >
>> =C2=A0=C2=A0=C2=A0 > On Mon, Dec 4, 2023 at 4:04=E2=80=AFAM Noe= l Butler
>> =C2=A0=C2=A0=C2=A0 <noel.butler@ausics.net&g= t; wrote:
>> =C2=A0=C2=A0=C2=A0 >> Thanks, it seems they are trying it on= then :)
>> =C2=A0=C2=A0=C2=A0 >>
>> =C2=A0=C2=A0=C2=A0 >> On 04/12/2023 10:44, J Pan wrote:
>> =C2=A0=C2=A0=C2=A0 >>
>> =C2=A0=C2=A0=C2=A0 >> starlink advertises its customer ip ad= dress location at
>> =C2=A0=C2=A0=C2=A0 >> http://geoip.= starlinkisp.net (not always updated but good
>> enough in
>> =C2=A0=C2=A0=C2=A0 >> most cases and traceroute can confirm = to some extent as well)
>> =C2=A0=C2=A0=C2=A0 >> --
>> =C2=A0=C2=A0=C2=A0 >> J Pan, UVic CSc, ECS566, 250-472-5796 = (NO VM), Pan@UVic.CA,
>> =C2=A0=C2=A0=C2=A0 Web.UVic.CA/~pan <http://Web.UVic.CA/~pan>
>> =C2=A0=C2=A0=C2=A0 >>
>> =C2=A0=C2=A0=C2=A0 >> On Sun, Dec 3, 2023 at 4:15=E2=80=AFPM= Noel Butler via Starlink
>> =C2=A0=C2=A0=C2=A0 >> <starlink@li= sts.bufferbloat.net> wrote:
>> =C2=A0=C2=A0=C2=A0 >>
>> =C2=A0=C2=A0=C2=A0 >>
>> =C2=A0=C2=A0=C2=A0 >> I run an open access usenet server, bu= t only for those within
>> =C2=A0=C2=A0=C2=A0 my CC, so access is by IP based on our CC alloc= ations from APNIC.
>> =C2=A0=C2=A0=C2=A0 >>
>> =C2=A0=C2=A0=C2=A0 >> Because IPv4 exhaustion this changes s= ometimes with buying
>> =C2=A0=C2=A0=C2=A0 allocations from other regions, and if they get= denied access I
>> =C2=A0=C2=A0=C2=A0 encourage them to let us know so we can keep AC= L's updated, I've
>> =C2=A0=C2=A0=C2=A0 had a request from a starlink user who claims t= hey are here, but
>> =C2=A0=C2=A0=C2=A0 traceroute shows them in .DE
>> =C2=A0=C2=A0=C2=A0 >>
>> =C2=A0=C2=A0=C2=A0 >> tracing some 217.foo.ad.dr
>> =C2=A0=C2=A0=C2=A0 >>
>> =C2=A0=C2=A0=C2=A0 >> ...
>> =C2=A0=C2=A0=C2=A0 >> 9 ae-6.r21.frnkge13.de.bb.gin.ntt.net
>> =C2=A0=C2=A0=C2=A0 <http= ://ae-6.r21.frnkge13.de.bb.gin.ntt.net> (129.250.3.183)
>> =C2=A0=C2=A0=C2=A0 290.223 ms 290.180 ms ae-1.r20.frnkge13.de.bb.gin.ntt.net
>> =C2=A0=C2=A0=C2=A0 <http= ://ae-1.r20.frnkge13.de.bb.gin.ntt.net> (129.250.7.35)
>> 280.523 ms
>> =C2=A0=C2=A0=C2=A0 >> 10 ae-1.a03.frnkge13.de.bb.gin.ntt.net
>> =C2=A0=C2=A0=C2=A0 <http= ://ae-1.a03.frnkge13.de.bb.gin.ntt.net> (129.250.3.152)
>> =C2=A0=C2=A0=C2=A0 290.109 ms 289.667 ms 292.864 ms
>> =C2=A0=C2=A0=C2=A0 >> 11 ae-0.spacex.frnkge13.de.bb.gin.ntt.net
>> =C2=A0=C2=A0=C2=A0 <h= ttp://ae-0.spacex.frnkge13.de.bb.gin.ntt.net> (213.198.72.19)
>> =C2=A0=C2=A0=C2=A0 279.611 ms 278.840 ms 279.592 ms
>> =C2=A0=C2=A0=C2=A0 >> 12 undefined.hostname.localhost (206.2= 24.65.189) 280.127 ms
>> =C2=A0=C2=A0=C2=A0 278.506 ms 284.265 ms
>> =C2=A0=C2=A0=C2=A0 >> 13 undefined.hostname.localhost (206.2= 24.65.209) 284.198 ms
>> =C2=A0=C2=A0=C2=A0 undefined.hostname.localhost (206.224.65.201) 2= 74.663 ms 273.073 ms
>> =C2=A0=C2=A0=C2=A0 >> 14 * * *
>> =C2=A0=C2=A0=C2=A0 >>
>> =C2=A0=C2=A0=C2=A0 >>
>> =C2=A0=C2=A0=C2=A0 >> As it is our policy to not collect any= user info or issue
>> =C2=A0=C2=A0=C2=A0 user/pass's and=C2=A0 only allow access by = IP, I'm hoping someone here
>> =C2=A0=C2=A0=C2=A0 knows if they are full of it, or does starlink = really assign
>> =C2=A0=C2=A0=C2=A0 addresses from anywhere? That one hardly makes = sense for user
>> =C2=A0=C2=A0=C2=A0 experience, or maybe starlink has so few users = in this country
>> =C2=A0=C2=A0=C2=A0 they haven't bothered changing anything yet= ?
>> =C2=A0=C2=A0=C2=A0 >>
>> =C2=A0=C2=A0=C2=A0 >> --
>> =C2=A0=C2=A0=C2=A0 >>
>> =C2=A0=C2=A0=C2=A0 >> Regards,
>> =C2=A0=C2=A0=C2=A0 >> Noel Butler
>> =C2=A0=C2=A0=C2=A0 >>
>> =C2=A0=C2=A0=C2=A0 >>
>> =C2=A0=C2=A0=C2=A0 >> ______________________________________= _________
>> =C2=A0=C2=A0=C2=A0 >> Starlink mailing list
>> =C2=A0=C2=A0=C2=A0 >> Starlink@lists.= bufferbloat.net
>> =C2=A0=C2=A0=C2=A0 >> https://lists.bufferbloat.net/listinfo/starlink
>> =C2=A0=C2=A0=C2=A0 >>
>> =C2=A0=C2=A0=C2=A0 >>
>> =C2=A0=C2=A0=C2=A0 >> --
>> =C2=A0=C2=A0=C2=A0 >>
>> =C2=A0=C2=A0=C2=A0 >> Regards,
>> =C2=A0=C2=A0=C2=A0 >> Noel Butler
>> =C2=A0=C2=A0=C2=A0 >>
>> =C2=A0=C2=A0=C2=A0 >>
>> =C2=A0=C2=A0=C2=A0 > __________________________________________= _____
>> =C2=A0=C2=A0=C2=A0 > Starlink mailing list
>> =C2=A0=C2=A0=C2=A0 > Starlink@lists.buff= erbloat.net
>> =C2=A0=C2=A0=C2=A0 > https://lists.bufferbloat.net/listinfo/starlink
>> =C2=A0=C2=A0=C2=A0 _______________________________________________=
>> =C2=A0=C2=A0=C2=A0 Starlink mailing list
>> =C2=A0=C2=A0=C2=A0 Starlink@lists.bufferblo= at.net
>> =C2=A0=C2=A0=C2=A0 htt= ps://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/l= istinfo/starlink
--000000000000c3236d060c013aec--