From: Dave Taht <dave.taht@gmail.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: David Lang <david@lang.hm>,
Cake List <cake@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cake] [Bloat] starlink testing
Date: Tue, 20 Apr 2021 08:48:17 -0700 [thread overview]
Message-ID: <CAA93jw7=wV6hvgKTwVa6mTpLgJnHBuVX74-aSNSXzxHm-MPzaA@mail.gmail.com> (raw)
In-Reply-To: <21914.1618927798@localhost>
I'm still busy doing more and more sophisticated tests and packet
captures. I am inclined to "go dark" for a while whilst I do that, but
if anyone would like to help re-write the ultimate blog entry, or
help out on instrumenting more tests, please contact me offlist.
Apparently there is IPv6 under test... somewhere... according to
reddit. Tunnelling my ipv6 via wireguard "just worked", so there's
that. There have been a few other surprises, one rather major.
As much as I dislike the cgnat I don't see how starlink had any other
choice, and the layer below that is hopefully capable of carrying
ipv6 well.
On Tue, Apr 20, 2021 at 7:10 AM Michael Richardson <mcr@sandelman.ca> wrote:
>
> David Lang <david@lang.hm> wrote:
> > I haven't seen any follow-ups where anyone has gotten a login to the dish or
> > has sniffed the traffic between the dish and the router.
>
> True, I haven't heard, but I haven't been looking.
>
> > I haven't seen anything that would show that the router has (or doesn't have)
> > any awareness of the satellite network.
>
> With multi-hundred antenna to be steered, and an AMD64 CPU on board, I can't
> imagine that that CPU isn't doing some significant amount of DSP.
> If they had offboarded all the analog parts to another DSP or discrete logic,
> then probably they wouldn't need a 64-bit CPU onboard: they could have used
> something slower/cheaper. Well, maybe there is future proofing involved.
>
> I'm very disappointed that "Something simpler than IPv6" turned out to be "CGN".
>
> --
> ] Never tell me the odds! | ipv6 mesh networks [
> ] Michael Richardson, Sandelman Software Works | IoT architect [
> ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
>
--
"For a successful technology, reality must take precedence over public
relations, for Mother Nature cannot be fooled" - Richard Feynman
dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
next prev parent reply other threads:[~2021-04-20 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 13:56 [Cake] " Dave Taht
2021-04-19 18:00 ` [Cake] [Bloat] " David Lang
2021-04-19 21:10 ` Michael Richardson
2021-04-19 21:42 ` David Lang
2021-04-20 14:09 ` Michael Richardson
2021-04-20 15:48 ` Dave Taht [this message]
2021-04-20 16:03 ` Michael Richardson
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw7=wV6hvgKTwVa6mTpLgJnHBuVX74-aSNSXzxHm-MPzaA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=david@lang.hm \
--cc=mcr@sandelman.ca \
/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