<div dir="auto">Dishy gets a /64 and I've tested DHCPv6 on both my Firewalla and my USG. They do prefix delegation to distribute that as a /56 locally.<div dir="auto"><br></div><div dir="auto">No NAT required for IPv6 (incoming or outgoing) connections. And there doesn't appear to be any restrictions on IPv6 traffic.</div><div dir="auto"><br></div><div dir="auto">This is with the round Dishy.<br><br><div data-smartmail="gmail_signature" dir="auto">Cheers,<br>Freddie<br><br>Typos due to smartphone keyboard.</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Dec 7, 2023, 3:54 a.m. Alexandre Petrescu via Starlink <<a href="mailto:starlink@lists.bufferbloat.net">starlink@lists.bufferbloat.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Le 04/12/2023 à 19:17, J Pan via Starlink a écrit :<br>
> yes, starlink does respond to its customers' complaints, although<br>
> sometimes slowly. its ipv4 address acquisition is scattered around as<br>
> a latecomer to the isp world, and as a global local isp, it's more<br>
> troublesome. ip packets have to be tunneled back to its home pop where<br>
> nat and other functions happen, sometimes around the world, causing a<br>
> much higher minimum rtt fluctuation in 15-second handover<br>
> intervals---bad for network protocols and applications. ipv6 can do<br>
> better but currently follows the same route as ipv4---an incentive to<br>
> promote ipv6 ;-)<br>
<br>
Excellent incentive!<br>
<br>
It would be good to know whether the dishy router obtains a /56 or a /64 <br>
prefix from the starlink ISP. That is easy to find out by just looking <br>
at the packets. This would tell whether a NAT can be avoided at home, <br>
and hence more apps made possible.<br>
<br>
IT would also be good to know whether the claimed IPv6 access on dishy <br>
is via a tunnel (IPv6 in IPv6, or IPv6 in IPv4) or it is 'native' (no <br>
tunnel). That will tell many things about additional latency that might <br>
be brought in by IPv6. (we'd want less latency, not more).<br>
<br>
After that, one can look more at promoting IPv6. Otherwise, IPv6 might <br>
still look as a hurdle, an obstacle, additional work that is too little <br>
necessary, or might even be worse than IPv4.<br>
<br>
Alex<br>
<br>
> --<br>
> J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, <a href="http://Web.UVic.CA/~pan" rel="noreferrer noreferrer" target="_blank">Web.UVic.CA/~pan</a><br>
><br>
> On Mon, Dec 4, 2023 at 4:04 AM Noel Butler <<a href="mailto:noel.butler@ausics.net" target="_blank" rel="noreferrer">noel.butler@ausics.net</a>> wrote:<br>
>> Thanks, it seems they are trying it on then :)<br>
>><br>
>> On 04/12/2023 10:44, J Pan wrote:<br>
>><br>
>> starlink advertises its customer ip address location at<br>
>> <a href="http://geoip.starlinkisp.net" rel="noreferrer noreferrer" target="_blank">http://geoip.starlinkisp.net</a> (not always updated but good enough in<br>
>> most cases and traceroute can confirm to some extent as well)<br>
>> --<br>
>> J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, <a href="http://Web.UVic.CA/~pan" rel="noreferrer noreferrer" target="_blank">Web.UVic.CA/~pan</a><br>
>><br>
>> On Sun, Dec 3, 2023 at 4:15 PM Noel Butler via Starlink<br>
>> <<a href="mailto:starlink@lists.bufferbloat.net" target="_blank" rel="noreferrer">starlink@lists.bufferbloat.net</a>> wrote:<br>
>><br>
>><br>
>> 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.<br>
>><br>
>> 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<br>
>><br>
>> tracing some 217.foo.ad.dr<br>
>><br>
>> ...<br>
>> 9 <a href="http://ae-6.r21.frnkge13.de.bb.gin.ntt.net" rel="noreferrer noreferrer" target="_blank">ae-6.r21.frnkge13.de.bb.gin.ntt.net</a> (129.250.3.183) 290.223 ms 290.180 ms <a href="http://ae-1.r20.frnkge13.de.bb.gin.ntt.net" rel="noreferrer noreferrer" target="_blank">ae-1.r20.frnkge13.de.bb.gin.ntt.net</a> (129.250.7.35) 280.523 ms<br>
>> 10 <a href="http://ae-1.a03.frnkge13.de.bb.gin.ntt.net" rel="noreferrer noreferrer" target="_blank">ae-1.a03.frnkge13.de.bb.gin.ntt.net</a> (129.250.3.152) 290.109 ms 289.667 ms 292.864 ms<br>
>> 11 <a href="http://ae-0.spacex.frnkge13.de.bb.gin.ntt.net" rel="noreferrer noreferrer" target="_blank">ae-0.spacex.frnkge13.de.bb.gin.ntt.net</a> (213.198.72.19) 279.611 ms 278.840 ms 279.592 ms<br>
>> 12 undefined.hostname.localhost (206.224.65.189) 280.127 ms 278.506 ms 284.265 ms<br>
>> 13 undefined.hostname.localhost (206.224.65.209) 284.198 ms undefined.hostname.localhost (206.224.65.201) 274.663 ms 273.073 ms<br>
>> 14 * * *<br>
>><br>
>><br>
>> 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?<br>
>><br>
>> --<br>
>><br>
>> Regards,<br>
>> Noel Butler<br>
>><br>
>><br>
>> _______________________________________________<br>
>> Starlink mailing list<br>
>> <a href="mailto:Starlink@lists.bufferbloat.net" target="_blank" rel="noreferrer">Starlink@lists.bufferbloat.net</a><br>
>> <a href="https://lists.bufferbloat.net/listinfo/starlink" rel="noreferrer noreferrer" target="_blank">https://lists.bufferbloat.net/listinfo/starlink</a><br>
>><br>
>><br>
>> --<br>
>><br>
>> Regards,<br>
>> Noel Butler<br>
>><br>
>><br>
> _______________________________________________<br>
> Starlink mailing list<br>
> <a href="mailto:Starlink@lists.bufferbloat.net" target="_blank" rel="noreferrer">Starlink@lists.bufferbloat.net</a><br>
> <a href="https://lists.bufferbloat.net/listinfo/starlink" rel="noreferrer noreferrer" target="_blank">https://lists.bufferbloat.net/listinfo/starlink</a><br>
_______________________________________________<br>
Starlink mailing list<br>
<a href="mailto:Starlink@lists.bufferbloat.net" target="_blank" rel="noreferrer">Starlink@lists.bufferbloat.net</a><br>
<a href="https://lists.bufferbloat.net/listinfo/starlink" rel="noreferrer noreferrer" target="_blank">https://lists.bufferbloat.net/listinfo/starlink</a><br>
</blockquote></div>