From: Nathan Owens <nathan@nathan.io>
To: Darrell Budic <budic@onholyground.com>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] v6 is back near Chicago, sort of
Date: Wed, 16 Feb 2022 09:46:41 -0800 [thread overview]
Message-ID: <CALjsLJu3fJoBk-Y4t8ToRF-YvhN8S0BZ7rYL++eSgY5zkpLv8w@mail.gmail.com> (raw)
In-Reply-To: <82154B47-D33C-4BFE-95ED-C5EEFE4220CD@onholyground.com>
[-- 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 --]
next prev parent reply other threads:[~2022-02-16 17:46 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 [this message]
2022-02-16 18:05 ` Darrell Budic
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=CALjsLJu3fJoBk-Y4t8ToRF-YvhN8S0BZ7rYL++eSgY5zkpLv8w@mail.gmail.com \
--to=nathan@nathan.io \
--cc=budic@onholyground.com \
--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