Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <davet@teklibre.net>
To: Jared Mauch <jared@puck.nether.net>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] dslreports speedtest
Date: Tue, 29 Jun 2021 10:52:16 -0700	[thread overview]
Message-ID: <B175725A-C6C0-4194-A02F-DFF49FD968B9@teklibre.net> (raw)
In-Reply-To: <YNpPb1S7egGxULCm@puck.nether.net>

Dear Jared:

if this is a wired result (it doesn’t look like it to me but it won’t be the first time I had confirmation bias!!), well, sigh.

1) Regardless, could you take a packet capture while re-running that dslreports test and put it somewhere we can get at?

The tcp rtt stats are good to look at in wireshark.

I typically just capture via

tcpdump -i myinterface -s 128 -w whatever.cap -n

2) Please don’t use the raspi’s 4’s wifi? It has horrifically bad bufferbloat in the first place, and there have been other reported bugs involving it’s multicast implementation taking down whole networks.

3) what the wifi chip and OS was driving this test? The uplink bufferbloat has some major spikes but if you look at the detailed report that might be misleading.

> On Jun 28, 2021, at 3:38 PM, Jared Mauch <jared@puck.nether.net> wrote:
> 
> 	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


  parent reply	other threads:[~2021-06-29 17:52 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
2021-06-29 17:33   ` Dave Taht
2021-06-29 17:52   ` Dave Taht [this message]
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=B175725A-C6C0-4194-A02F-DFF49FD968B9@teklibre.net \
    --to=davet@teklibre.net \
    --cc=jared@puck.nether.net \
    --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