Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Ulrich Speidel <u.speidel@auckland.ac.nz>,
	David Lang <david@lang.hm>,
	 "starlink@lists.bufferbloat.net"
	<starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink hidden buffers
Date: Sun, 14 May 2023 02:13:02 -0700 (PDT)	[thread overview]
Message-ID: <p5024n1o-301n-2554-2600-94npn9nq8p51@ynat.uz> (raw)
In-Reply-To: <A85E4E9D-95EE-40E2-8856-184AC3153853@gmx.de>

On Sun, 14 May 2023, Sebastian Moeller wrote:

> silly question, does starlink operate using fixed geographical cells and are 
> CPE/dishies assigned to a single cell? In which case handover would not have 
> to be so bad, the satellite leaving a cell is going to shed all its load and 
> is going to take over the previous satellite's load in the cell it just starts 
> serving. Assuming equal "air-conditions" the modulation scheme should be 
> similar. So wouldn't the biggest problem be the actual switch-over time 
> required for dishies to move from one satellite to the next (and would this be 
> in line with the reported latency spikes every 15 seconds)?

yes, there was a paper not that long ago from someone who was using the starlink 
signal for time/location purposes that detailed the protocol and the coverage 
(at least at that time)

in the last week or so the FCC approved increased power/utilization percentage, 
I don't know if units in the field have been modified to use it yet.

>
>> On May 14, 2023, at 10:43, Ulrich Speidel via Starlink <starlink@lists.bufferbloat.net> wrote:
>>
>> On 14/05/2023 6:55 pm, David Lang wrote:
>>>
>>> I just discovered that someone is manufacturing an adapter so you no longer have
>>> to cut the cable
>>>
>>> https://www.amazon.com/YAOSHENG-Rectangular-Adapter-Connect-Injector/dp/B0BYJTHX4P
>>>
>> I'll see whether I can get hold of one of these. Cutting a cable on a university IT asset as an academic is not allowed here, except if it doesn't meet electrical safety standards.
>
> 	[SM] There must be a way to get this accomplished with in regulations if 
> the test requiring this is somehow made part of the experiment, no? (Maybe 
> requires partnering with other faculties like electrical engineering to get 
> the necessary clout with the administration?)

the other optin would be to order a second cord and cut that. You then aren't 
modifying the IT asset.

David Lang

  reply	other threads:[~2023-05-14  9:13 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-13 10:10 Ulrich Speidel
2023-05-13 11:20 ` Sebastian Moeller
2023-05-13 12:16   ` Ulrich Speidel
2023-05-13 23:00     ` David Lang
2023-05-13 22:57 ` David Lang
2023-05-14  6:06   ` Ulrich Speidel
2023-05-14  6:55     ` David Lang
2023-05-14  8:43       ` Ulrich Speidel
2023-05-14  9:00         ` David Lang
2023-05-15  2:41           ` Ulrich Speidel
2023-05-15  3:33             ` David Lang
2023-05-15  6:36               ` Sebastian Moeller
2023-05-15 11:07                 ` David Lang
2023-05-24 12:55               ` Ulrich Speidel
2023-05-24 13:44                 ` Dave Taht
2023-05-24 14:05                   ` David Lang
2023-05-24 14:49                   ` Michael Richardson
2023-05-24 15:09                     ` Dave Collier-Brown
2023-05-24 15:31                     ` Dave Taht
2023-05-24 18:30                       ` Michael Richardson
2023-05-24 18:45                         ` Sebastian Moeller
2023-05-24 13:59                 ` David Lang
2023-05-24 22:39                   ` Ulrich Speidel
2023-05-25  0:06                     ` David Lang
2023-07-27 20:37                     ` Ulrich Speidel
2023-05-24 15:18                 ` Mark Handley
2023-05-24 21:50                   ` Ulrich Speidel
2023-05-25  0:17                     ` David Lang
2023-05-14  9:06         ` Sebastian Moeller
2023-05-14  9:13           ` David Lang [this message]
2023-05-14  9:57 ` Oleg Kutkov
2023-05-14  9:59   ` Oleg Kutkov
2023-05-24 15:26 ` Bjørn Ivar Teigen
2023-05-24 21:53   ` Ulrich Speidel

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=p5024n1o-301n-2554-2600-94npn9nq8p51@ynat.uz \
    --to=david@lang.hm \
    --cc=moeller0@gmx.de \
    --cc=starlink@lists.bufferbloat.net \
    --cc=u.speidel@auckland.ac.nz \
    /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