From: Oleg Kutkov <contact@olegkutkov.me>
To: Jonathan Bennett <jonathanbennett@hackaday.com>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] First tests of the Starlink REV4 (aka gen3)
Date: Thu, 25 Jan 2024 01:50:59 +0200 [thread overview]
Message-ID: <895f12d4-9941-484d-aca1-05f988a4be59@olegkutkov.me> (raw)
In-Reply-To: <CAHtUBujyeSi_zENtk=XvdfqdP-Ty_H5Sxa4t4BPuhZ8LxJFdMA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2414 bytes --]
The PoE "standard" is the same.
Thus, you can power the new terminal with any Starlink PoE injector
(even REV1).
On 1/25/24 01:40, Jonathan Bennett wrote:
> I'm mainly curious if the move back to RJ45 means they are now using a
> real POE standard, instead of the custom solution the previous
> generations have used.
>
> Jonathan Bennett
> Hackaday.com
>
>
> On Wed, Jan 24, 2024 at 4:47 PM Oleg Kutkov via Starlink
> <starlink@lists.bufferbloat.net> wrote:
>
> I will try to do better tests this weekend, measuring all the
> necessary
> parameters. Plus IPv6
>
> On 1/24/24 14:37, Alexandre Petrescu via Starlink wrote:
> > Thanks for the tests!
> >
> > The dl/ul speeds 300/15 mbit/s are impressive.
> >
> > At video pointer 5:53 the reported Ping ?/dl/ul 88/204/121 ms and
> > Jitter 9.2 ms seem interesting.
> >
> > ==> I am not sure which of the two (ping or jitter) you name
> > 'latency'?
> >
> > ==> I am not sure why the dl (download) ping ms is higher
> than the
> > ul.
> >
> > ==> I don't know what is the first ('?') parameter reported as
> > 88ms for Ping?
> >
> > I wonder whether the DHCPv6-PD is still supported by REV4 and
> whether
> > the allocated prefix is still a non-/64 (i.e. a /56 delivered by
> > DHCPv6-PD reported earlier on this email list by Steven on Dec. 12,
> > 2023)?
> >
> > Alex
> >
> > Le 23/01/2024 à 10:07, Oleg Kutkov via Starlink a écrit :
> >> I conducted the initial comparative tests of the new terminal in
> >> Ukraine. I guess it's not a really "legal" because the new
> terminal
> >> is not certified and not selling outside the US for the moment.
> But
> >> who cares.
> >>
> >> Here's a video: https://youtu.be/hWPMpJrjd1g
> >>
> >> I will try to do more technical tests next week. There will be
> a new
> >> video.
> >>
> > _______________________________________________
> > Starlink mailing list
> > Starlink@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/starlink
>
> --
> Best regards,
> Oleg Kutkov
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
--
Best regards,
Oleg Kutkov
[-- Attachment #1.2: Type: text/html, Size: 5194 bytes --]
[-- Attachment #2: rev4_poe.jpg --]
[-- Type: image/jpeg, Size: 135882 bytes --]
next prev parent reply other threads:[~2024-01-24 23:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 9:07 Oleg Kutkov
2024-01-24 12:37 ` Alexandre Petrescu
2024-01-24 22:47 ` Oleg Kutkov
2024-01-24 23:40 ` Jonathan Bennett
2024-01-24 23:50 ` Oleg Kutkov [this message]
2024-01-25 1:29 ` David Lang
2024-01-25 1:54 ` Ulrich Speidel
2024-02-22 12:18 ` Alexandre Petrescu
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=895f12d4-9941-484d-aca1-05f988a4be59@olegkutkov.me \
--to=contact@olegkutkov.me \
--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