From: Bruce Perens <bruce@perens.com>
To: Jonathan Bennett <jonathanbennett@hackaday.com>
Cc: David Lang <david@lang.hm>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Electric power for Dishy
Date: Mon, 18 Apr 2022 17:42:17 -0700 [thread overview]
Message-ID: <CAK2MWOsU=eCNRgFG_ax-Z+D+iJG6+b_E8kGLov7UjtzgkxqnPw@mail.gmail.com> (raw)
In-Reply-To: <CAK2MWOtAnoFA92yyPb2Lz3DfXUU4KXLg3yAGxDq0S5KpJK1XxA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 845 bytes --]
There is also the potential to crack open the router and simply provide
50V:
https://olegkutkov.me/2022/04/10/initial-analysis-of-the-starlink-router-gen2/
On Mon, Apr 18, 2022 at 5:33 PM Bruce Perens <bruce@perens.com> wrote:
> The hacks seem to have been for circular Dishy. This link provides a path
> that might work to bring out the power leads for rectangular Dishy, but
> unfortunately they did not just make it possible to plug POE in.
> https://olegkutkov.me/2022/03/07/reverse-engineering-of-the-starlink-ethernet-adapter/
>
> Thanks
>
> Bruce
>
> On Mon, Apr 18, 2022 at 5:13 PM Jonathan Bennett <
> jonathanbennett@hackaday.com> wrote:
>
>> There's a post on Reddit describing a custom solution:
>> https://www.reddit.com/r/Starlink/comments/sb4dei/homebrew_poeethernet_adapter_for_rectangle/
>>
>
>
--
Bruce Perens K6BP
[-- Attachment #2: Type: text/html, Size: 1951 bytes --]
next prev parent reply other threads:[~2022-04-19 0:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 1:39 [Starlink] an rtt_fair test? Dave Taht
2022-04-17 14:35 ` jordan
2022-04-17 14:56 ` Dave Taht
2022-04-17 15:36 ` jordan
2022-04-17 16:54 ` [Starlink] [Bloat] " Daniel Sterling
2022-04-18 0:22 ` [Starlink] " Dave Taht
2022-04-19 0:06 ` [Starlink] Electric power for Dishy Bruce Perens
2022-04-19 0:09 ` David Lang
2022-04-19 0:13 ` Jonathan Bennett
2022-04-19 0:33 ` Bruce Perens
2022-04-19 0:42 ` Bruce Perens [this message]
2022-04-19 0:45 ` Jonathan Bennett
2022-04-19 3:42 ` Mike Puchol
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='CAK2MWOsU=eCNRgFG_ax-Z+D+iJG6+b_E8kGLov7UjtzgkxqnPw@mail.gmail.com' \
--to=bruce@perens.com \
--cc=david@lang.hm \
--cc=jonathanbennett@hackaday.com \
--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