From: Dave Taht <dave.taht@gmail.com>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] I wish we could bring packet captures back
Date: Fri, 10 Mar 2023 15:51:31 -0800 [thread overview]
Message-ID: <CAA93jw4VE88RLFDNDnBzrvjdUUydHpopAGko2StXO_hR-YKmmg@mail.gmail.com> (raw)
I figure the measured bloat on this plane flight was at least in part,
due to spotty connectivity.
https://twitter.com/Erdayastronaut/status/1634202410808754177
But over on my talk this past week I pointed at some methods on
ookla's test I found odd, and did a live videoconference over mine.
https://www.youtube.com/watch?v=tAVwmUG21OY&t=5715s
--
Come Heckle Mar 6-9 at: https://www.understandinglatency.com/
Dave Täht CEO, TekLibre, LLC
reply other threads:[~2023-03-10 23:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAA93jw4VE88RLFDNDnBzrvjdUUydHpopAGko2StXO_hR-YKmmg@mail.gmail.com \
--to=dave.taht@gmail.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