From: Darrell Budic <budic@onholyground.com>
To: Nathan Owens <nathan@nathan.io>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] v6 is back near Chicago, sort of
Date: Wed, 16 Feb 2022 12:05:08 -0600 [thread overview]
Message-ID: <E5AA01C8-A60C-4A11-9BC6-B29657F70DA4@onholyground.com> (raw)
In-Reply-To: <CALjsLJu3fJoBk-Y4t8ToRF-YvhN8S0BZ7rYL++eSgY5zkpLv8w@mail.gmail.com>
[-- 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 --]
prev parent reply other threads:[~2022-02-16 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 17:45 Darrell Budic
2022-02-16 17:46 ` Nathan Owens
2022-02-16 18:05 ` Darrell Budic [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E5AA01C8-A60C-4A11-9BC6-B29657F70DA4@onholyground.com \
--to=budic@onholyground.com \
--cc=nathan@nathan.io \
--cc=starlink@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox