From: Larry Press <lpress@csudh.edu>
To: "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: [Starlink] Reverse engineering of V2 router from photos
Date: Sun, 10 Apr 2022 02:28:01 +0000 [thread overview]
Message-ID: <BYAPR03MB38637614131E17A5FA7B7290C2EB9@BYAPR03MB3863.namprd03.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 702 bytes --]
https://olegkutkov.me/2022/04/10/initial-analysis-of-the-starlink-router-gen2/
How will this router impact performance?
Also -- does anyone have information on the "premium" terminal and router?
[https://olegkutkov.me/wp-content/uploads/2022/03/starlink_router2_mesh_page.jpg]<https://olegkutkov.me/2022/04/10/initial-analysis-of-the-starlink-router-gen2/>
Initial analysis of the Starlink router gen2<https://olegkutkov.me/2022/04/10/initial-analysis-of-the-starlink-router-gen2/>
It was fun to do reverse engineering of the original Starlink router. The article was also well received. Sure, it would be great to do the same thing with the new Starlink router gen2. It’s …
olegkutkov.me
[-- Attachment #2: Type: text/html, Size: 3901 bytes --]
reply other threads:[~2022-04-10 2:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BYAPR03MB38637614131E17A5FA7B7290C2EB9@BYAPR03MB3863.namprd03.prod.outlook.com \
--to=lpress@csudh.edu \
--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