General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Michael Richardson <mcr@sandelman.ca>
Cc: 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: Mon, 19 Apr 2021 14:42:58 -0700 (PDT)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.2104191439590.18176@qynat-yncgbc> (raw)
In-Reply-To: <10241.1618866642@localhost>

I've watched those, and it's PoE communication to the dish, and there is a 
processor on the dish with a serial console.

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.

I haven't seen anything that would show that the router has (or doesn't have) 
any awareness of the satellite network.

That's why I was asking about sniffing between the devices to see what's 
happening there.

David Lang

On Mon, 19 Apr 2021, Michael Richardson wrote:

> David Lang <david@lang.hm> wrote:
>    > are you able to sniff between the router and the dish? I'm curious how much
>    > of the smarts is in the dish vs the router. My hope is that the router is
>    > just a conventional router with the satellite network smarts in the dish.
>
> No.
> See the teardowns, such as: https://www.youtube.com/watch?v=QudtSo5tpLk
> It's a huge synthetic antenna.  It's openwrt though.
>
>

  reply	other threads:[~2021-04-19 21:42 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 [this message]
2021-04-20 14:09       ` Michael Richardson
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=nycvar.QRO.7.76.6.2104191439590.18176@qynat-yncgbc \
    --to=david@lang.hm \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --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