From: Brenton Roskopf <notnerb84@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] Starlink bufferbloat
Date: Mon, 17 May 2021 23:19:31 -0500 [thread overview]
Message-ID: <CABjqX4y1R-GLCRN2QZ1T3HWbrn6ZYDxmj41xoOKWRTk936dYHQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 999 bytes --]
I, too, have noticed inordinate amounts of latency concurrent with
aggressive file transfers and speed tests (with some healthy losses,
occasionally). Anything I can do to help with testing? Anywhere I can
"upvote" a support ticket or something? Already on:
https://starlinkstatus.space/stations
Not using the Starlink router. But have several openwrt instances (vm and
physical) and other routers connected over IPv4 CGNAT and IPv6 to the WAN
(I think 3 separate dual-stack configs and an IPv4-dedicated one). I am
also scripting dynamic DNS to godaddy if intra-network testing using iperf,
flent or some other tool is useful.
Just switched to 1.1.1.1 for DNS and seeing the DoH traffic, but, sadly,
haven't really noticed much relief. Recent dishy updates seem to have
improved things, but I did need to make significant tweaks to sysctl.conf
on my public-facing Linux VM in order to get decent speedtests using
speedtest-cli... Not really sure how to do that on a Windows system.
-the_notnerb
[-- Attachment #2: Type: text/html, Size: 1176 bytes --]
next reply other threads:[~2021-05-18 4:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 4:19 Brenton Roskopf [this message]
2023-08-31 20:08 [Starlink] Starlink Bufferbloat Luis A. Cornejo
2023-08-31 20:22 ` tom
2023-08-31 20:46 ` Luis A. Cornejo
2023-08-31 21:06 ` tom
2023-08-31 21:59 ` Spencer Sevilla
2023-09-01 6:39 ` Tom Zubko
2023-09-01 12:32 ` Luis A. Cornejo
2023-09-01 14:22 ` Tom Zubko
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=CABjqX4y1R-GLCRN2QZ1T3HWbrn6ZYDxmj41xoOKWRTk936dYHQ@mail.gmail.com \
--to=notnerb84@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