From: J Pan <Pan@uvic.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Marc Blanchet <marc.blanchet@viagenie.ca>,
Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] starlink at sea
Date: Sun, 14 Jul 2024 12:32:03 -0700 [thread overview]
Message-ID: <CAHn=e4iTz3Jztou-AkKULGVjj5Tm8vy-1cMXXyp9Qd5v5BgORQ@mail.gmail.com> (raw)
In-Reply-To: <11567.1720044376@obiwan.sandelman.ca>
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
per marc's permission. this is how the satellite link looked like (not
clear whether isl was involved) with the frankfurt pop. the behavior
around #3000 is likely due to the cruise wifi
--
J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan
On Wed, Jul 3, 2024 at 3:06 PM Michael Richardson via Starlink
<starlink@lists.bufferbloat.net> wrote:
>
>
> Marc Blanchet via Starlink <starlink@lists.bufferbloat.net> wrote:
> > FYI, Currently on a cruise (Silversea) in the Aegean Sea (Greece,
> > Mediterranean). Latency ~60ms,
>
> Under load?
> You have an apple device, I think, so what's the RPM?
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting )
> Sandelman Software Works Inc, Ottawa and Worldwide
>
>
>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
[-- Attachment #2: starlink-tests-3.png --]
[-- Type: image/png, Size: 170009 bytes --]
next prev parent reply other threads:[~2024-07-14 19:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 20:40 Dave Taht
2024-07-03 3:40 ` Ulrich Speidel
2024-07-03 17:21 ` Larry Press
2024-07-03 4:21 ` Marc Blanchet
2024-07-03 4:26 ` J Pan
2024-07-03 17:06 ` Larry Press
2024-07-03 22:06 ` Michael Richardson
2024-07-14 19:32 ` J Pan [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-14 0:20 Dave Taht
2022-07-14 0:31 ` David Lang
2022-07-14 0:36 ` Gary E. Miller
2022-07-14 0:40 ` David Lang
2022-07-14 0:59 ` Gary E. Miller
2022-07-14 1:36 ` David Lang
2022-07-14 5:46 ` Larry Press
2022-07-14 7:00 ` David Lang
2022-07-14 11:15 ` Mike Puchol
2022-07-14 11:32 ` Sebastian Moeller
2022-07-14 12:02 ` Mike Puchol
2022-07-14 12:34 ` Sebastian Moeller
2022-07-14 12:49 ` Nitinder Mohan
2022-07-14 12:57 ` Jared Mauch
2022-07-14 13:05 ` Nitinder Mohan
2022-07-14 13:33 ` Nitinder Mohan
2022-07-14 14:56 ` Mike Puchol
2022-07-14 15:28 ` Sebastian Moeller
2022-07-14 15:32 ` Nathan Owens
2022-07-27 21:17 ` 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='CAHn=e4iTz3Jztou-AkKULGVjj5Tm8vy-1cMXXyp9Qd5v5BgORQ@mail.gmail.com' \
--to=pan@uvic.ca \
--cc=marc.blanchet@viagenie.ca \
--cc=mcr+ietf@sandelman.ca \
--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