From: Dave Taht <dave.taht@gmail.com>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] some recent starlink waveform results
Date: Sat, 6 May 2023 08:43:14 -0700 [thread overview]
Message-ID: <CAA93jw7pT1C2uA6STT10SKKtzwcyUsRinNTR--=MFcyn4VzF0g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 306 bytes --]
I have been having difficulty trusting waveform´s uplink results for over 9
months now.
https://www.reddit.com/r/Starlink/comments/134fvis/starlink_and_bufferbloat_how_bad_is_yours/
--
Podcast:
https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/
Dave Täht CSO, LibreQos
[-- Attachment #2: Type: text/html, Size: 758 bytes --]
next reply other threads:[~2023-05-06 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 15:43 Dave Taht [this message]
2023-05-08 16:05 ` Livingood, Jason
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='CAA93jw7pT1C2uA6STT10SKKtzwcyUsRinNTR--=MFcyn4VzF0g@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