From: Jared Mauch <jared@puck.nether.net>
To: dickroy@alum.mit.edu
Cc: Nathan Owens <nathan@nathan.io>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] dslreports speedtest
Date: Mon, 28 Jun 2021 19:50:05 -0400 [thread overview]
Message-ID: <1EF494BA-D346-45FC-B9F1-7F93FE3A037D@puck.nether.net> (raw)
In-Reply-To: <6F9998BC34254E79864F5DECBC5A685E@SRA6>
[-- Attachment #1: Type: text/plain, Size: 2866 bytes --]
I plan to leave a raspi up here and have a way to get in and test it out remotely. We have been doing a lot of work on the solar to make sure it can run things 24x7 including the Maine winters as this is a remote area.
Sent from my TI-99/4a
> On Jun 28, 2021, at 7:18 PM, Dick Roy <dickroy@alum.mit.edu> wrote:
>
>
> Yes of course … pardon the BFOMP (“brain fart on my part”) :^(((((
>
> From: Nathan Owens [mailto:nathan@nathan.io]
> Sent: Monday, June 28, 2021 4:12 PM
> To: dickroy@alum.mit.edu
> Cc: Jared Mauch; starlink@lists.bufferbloat.net
> Subject: Re: [Starlink] dslreports speedtest
>
> That would be interesting to look at — To clarify, the latency blips are on 15 second intervals.
>
> On Mon, Jun 28, 2021 at 3:51 PM Dick Roy <dickroy@alum.mit.edu> wrote:
> If you have an obstructed view of the sky, it would be interesting to look
> at the test results as a function of time to see if the periodic 15 minuute
> latency blips you've all seen aren't replaced by a more sporadic/random set
> of satellite switching times.
>
> -----Original Message-----
> From: Starlink [mailto:starlink-bounces@lists.bufferbloat.net] On Behalf Of
> Jared Mauch
> Sent: Monday, June 28, 2021 3:39 PM
> To: starlink@lists.bufferbloat.net
> Subject: Re: [Starlink] dslreports speedtest
>
> my result if someone wants to look at it:
>
> http://www.dslreports.com/speedtest/68794590
>
> I'm about 40-50' away from the router which is outside with the
> solar panels and other gear. I'm inside and dishy is on the roof
> partially obstructed but somewhat better after some light application of
> the chainsaw.
>
> - jared
>
>
> On Mon, Jun 28, 2021 at 06:35:25PM -0400, Jared Mauch wrote:
> >
> > I went to go check my bufferbloat and it says:
> >
> > This connection is not satellite
> > latency of 45ms is too low
> > Test cancelled
> >
> > Kinda amusing.
> >
> > - Jared
> >
> > (e-mail sent over ssh via starlink)
> >
> > --
> > Jared Mauch | pgp key available via finger from jared@puck.nether.net
> > clue++; | http://puck.nether.net/~jared/ My statements are only
> mine.
> > _______________________________________________
> > Starlink mailing list
> > Starlink@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/starlink
>
> --
> Jared Mauch | pgp key available via finger from jared@puck.nether.net
> clue++; | http://puck.nether.net/~jared/ My statements are only mine.
> _______________________________________________
> 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
[-- Attachment #2: Type: text/html, Size: 7646 bytes --]
next prev parent reply other threads:[~2021-06-28 23:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 22:35 Jared Mauch
2021-06-28 22:38 ` Jared Mauch
2021-06-28 22:51 ` Dick Roy
2021-06-28 23:12 ` Nathan Owens
2021-06-28 23:17 ` Dick Roy
2021-06-28 23:50 ` Jared Mauch [this message]
2021-06-29 17:33 ` Dave Taht
2021-06-29 17:52 ` Dave Taht
2021-06-29 17:23 ` Dave Taht
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=1EF494BA-D346-45FC-B9F1-7F93FE3A037D@puck.nether.net \
--to=jared@puck.nether.net \
--cc=dickroy@alum.mit.edu \
--cc=nathan@nathan.io \
--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