From: Dave Taht <dave.taht@gmail.com>
To: Oleg Kutkov <contact@olegkutkov.me>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] oleg posts an archive of his starlink repairs in ukraine
Date: Mon, 28 Nov 2022 15:30:24 -0800 [thread overview]
Message-ID: <CAA93jw6xSBC0449de-Bq1Kj+zW27h2vh+waMc073Rv52QcSVEg@mail.gmail.com> (raw)
In-Reply-To: <f88f460e-97fe-764a-dd2a-87863798e30b@olegkutkov.me>
On Sun, Nov 27, 2022 at 5:03 PM Oleg Kutkov via Starlink
<starlink@lists.bufferbloat.net> wrote:
>
> Hello everybody,
>
> Thanks, Dave, for inviting me to this mailing list.
Thx for joining! Ton of old farts here that can't cope with twitter.
>
> I think someone already followed my blog or Twitter. I did a lot of work
> on the Starlink router and Dishy analysis and probably can tell
> something I didn't publish yet. Currently, I'm doing all these repairs
> due to the situation in my country.
What can we do to help?
> I have some ideas to make a custom version of the SpaceX Gen2 router
> with optimized OpenWrt and modified hardware.
The Gen1 would have been easier to modify - it had an out of the box
supported version of modern openwrt already.
The Gen2 was only supported by the manufacturer's devboard in openwrt
last I looked.
It would be nice to see more features on the Gen2 - BGP and an IGP,
for example, more ability to handle complex networks.
>
> On 11/28/22 02:52, Dave Taht via Starlink wrote:
> > Here: https://olegkutkov.me/starlink-repairs-archive/
> >
> > In addition to addressing the dire need to keep these devices
> > functioning, his efforts are the most stirring example of the
> > right-to-repair I've yet seen,
> > and also, the training and diagnostic lessons he's documented above
> > apply to so much other gear we could so easily be repairing, rather
> > than replacing.
> >
> >
> --
> Best regards,
> Oleg Kutkov
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
--
This song goes out to all the folk that thought Stadia would work:
https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
Dave Täht CEO, TekLibre, LLC
next prev parent reply other threads:[~2022-11-28 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 0:52 Dave Taht
2022-11-28 1:03 ` Oleg Kutkov
2022-11-28 23:30 ` Dave Taht [this message]
2022-11-28 3:52 ` Cory Doctorow
2022-11-29 4:05 ` Benjamin Henrion
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=CAA93jw6xSBC0449de-Bq1Kj+zW27h2vh+waMc073Rv52QcSVEg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=contact@olegkutkov.me \
--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