[Starlink] v6 is back near Chicago, sort of

[Starlink] v6 is back near Chicago, sort of

[Darrell Budic]

Looks like V6 got re-enabled for me around 12:30AM CST, didn’t notice if it was related to a firmware upgrade or not. 

Not super exciting, I know, but it doesn’t look like DHCP-pd is currently operating and my NetworkManger config was freaking out and crashing because it couldn’t get the -pd assignments. So it broke my starlink for the morning, and since NM took the dhclient out with it, the whole dishy looked broken. Sigh, at least it got my attention.

Anyway, passing it along as an item of interest, not nearly cool as some of the recent sat discussions have been :)

  -Darrell

Re: [Starlink] v6 is back near Chicago, sort of

[Nathan Owens]

[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]

If you have working IPv6, it likely means you are on the AS36492 network.
If you have no IPv6 and public IP, you are behind AS14593.

On Wed, Feb 16, 2022 at 9:45 AM Darrell Budic <budic@onholyground.com>
wrote:

> Looks like V6 got re-enabled for me around 12:30AM CST, didn’t notice if
> it was related to a firmware upgrade or not.
>
> Not super exciting, I know, but it doesn’t look like DHCP-pd is currently
> operating and my NetworkManger config was freaking out and crashing because
> it couldn’t get the -pd assignments. So it broke my starlink for the
> morning, and since NM took the dhclient out with it, the whole dishy looked
> broken. Sigh, at least it got my attention.
>
> Anyway, passing it along as an item of interest, not nearly cool as some
> of the recent sat discussions have been :)
>
>   -Darrell
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>

[-- Attachment #2: Type: text/html, Size: 1462 bytes --]

Re: [Starlink] v6 is back near Chicago, sort of

[Darrell Budic]

[-- Attachment #1: Type: text/plain, Size: 1443 bytes --]

Ah, interesting. You are correct, it’s flipped back behind AS36492 and my v4 is behind Googles CGNAT again. Going to have to look and see if I’m on a different ground station or something. Or maybe just watch and see if it switches back.

> On Feb 16, 2022, at 11:46 AM, Nathan Owens <nathan@nathan.io> wrote:
> 
> If you have working IPv6, it likely means you are on the AS36492 network. If you have no IPv6 and public IP, you are behind AS14593. 
> 
> On Wed, Feb 16, 2022 at 9:45 AM Darrell Budic <budic@onholyground.com <mailto:budic@onholyground.com>> wrote:
> Looks like V6 got re-enabled for me around 12:30AM CST, didn’t notice if it was related to a firmware upgrade or not. 
> 
> Not super exciting, I know, but it doesn’t look like DHCP-pd is currently operating and my NetworkManger config was freaking out and crashing because it couldn’t get the -pd assignments. So it broke my starlink for the morning, and since NM took the dhclient out with it, the whole dishy looked broken. Sigh, at least it got my attention.
> 
> Anyway, passing it along as an item of interest, not nearly cool as some of the recent sat discussions have been :)
> 
>   -Darrell
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net <mailto:Starlink@lists.bufferbloat.net>
> https://lists.bufferbloat.net/listinfo/starlink <https://lists.bufferbloat.net/listinfo/starlink>


[-- Attachment #2: Type: text/html, Size: 2367 bytes --]