From: "Dave Täht" <davet@teklibre.net>
To: David Lang <david@lang.hm>
Cc: Dave Taht <dave.taht@gmail.com>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] reverse engineering the starlink router
Date: Wed, 26 Jan 2022 19:46:39 +0000 [thread overview]
Message-ID: <20220126194639.GA15863@mail.taht.net> (raw)
In-Reply-To: <0p8o14o-57p0-9q2s-6424-osos35328q4q@ynat.uz>
David: Have you been getting anywhere?
https://forum.openwrt.org/t/cake-w-adaptive-bandwidth/108848/2320
is about as ready for starlink testing as we can get it.
On Mon, Jan 10, 2022 at 09:27:16PM -0800, David Lang wrote:
> The new square dish no longer uses a rj-45 cable between the dish and the
> router, they have some new connector (looks limilar to USB-C, but flared on
> one side like micro-USB)
>
> has anyone seen a teardown of the new dish/router yet? (I'm not willing to
> sacrafice my dish, but I may be willing to open the router for what little
> good it will do, but will probably wait until after I get the ethernet
> adapter first.
>
> David Lang
>
> On Mon, 10 Jan 2022, Dave Taht wrote:
>
> >Date: Mon, 10 Jan 2022 20:32:34 -0800
> >From: Dave Taht <dave.taht@gmail.com>
> >To: starlink@lists.bufferbloat.net
> >Subject: [Starlink] reverse engineering the starlink router
> >
> >Really good teardown and analysis here:
> >
> >https://olegkutkov.me/2021/12/25/analysis-and-reverse-engineering-of-the-original-starlink-router/
> >
> >According to his twitter feed, he's now deep into the dishy:
> >https://twitter.com/olegkutkov
> >
> >I really hope the original starlink router gets updated to a modern
> >openwrt. The offloads they presently use in that product are just not
> >needed at the speeds the dishy runs at and there are so many
> >advantages to that modern codebase.
> >
> >I did get a shot at the newer dishy and wifi router over the holiday
> >myself, (without, sigh, an ethernet port) but my primary interest is
> >merely in finding a way to effectively run fq-codel derived algos on
> >or near it and not have to tear it apart.
> >
> >
> >--
> >I tried to build a better future, a few times:
> >https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
> >
> >Dave Täht CEO, TekLibre, LLC
> >_______________________________________________
> >Starlink mailing list
> >Starlink@lists.bufferbloat.net
> >https://lists.bufferbloat.net/listinfo/starlink
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
prev parent reply other threads:[~2022-01-26 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 4:32 Dave Taht
2022-01-11 5:27 ` David Lang
2022-01-11 14:58 ` Nathan Owens
2022-01-26 19:46 ` Dave Täht [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=20220126194639.GA15863@mail.taht.net \
--to=davet@teklibre.net \
--cc=dave.taht@gmail.com \
--cc=david@lang.hm \
--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