General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: David Lang <david@lang.hm>, Dave Taht <dave.taht@gmail.com>,
	Cake List <cake@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] starlink testing
Date: Tue, 20 Apr 2021 10:09:58 -0400	[thread overview]
Message-ID: <21914.1618927798@localhost> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2104191439590.18176@qynat-yncgbc>

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    [


  reply	other threads:[~2021-04-20 14:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19 13:56 Dave Taht
2021-04-19 18:00 ` David Lang
2021-04-19 21:10   ` Michael Richardson
2021-04-19 21:42     ` David Lang
2021-04-20 14:09       ` Michael Richardson [this message]
2021-04-20 15:48         ` Dave Taht
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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=21914.1618927798@localhost \
    --to=mcr@sandelman.ca \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=david@lang.hm \
    /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