Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] starlink extensions over uk
Date: Mon, 25 Jul 2022 20:35:13 +1200	[thread overview]
Message-ID: <e3dd7bad-3dae-b64a-97bb-8e2e281c4011@auckland.ac.nz> (raw)
In-Reply-To: <CAA93jw7VfPd3BSDZ_cTM3wBWY0cdUKPBygkUVzcdCSUj2VVkqA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2469 bytes --]

I haven't got Mike's nice software but I got snail mail today, so let's 
try the back of one of the envelopes.

53 degrees north (where the existing constellation tops out) is roughly 
the latitude of Nottingham or Stoke-on-Trent. Note that this is also the 
latitude with the largest number of birds per km (or mile, if you so 
prefer) of parallel. They sit almost cheek to jowl there.

Now the northern tip of the UK's main islands is at around 59 degrees 
north - that's six degrees more. One degree of latitude is roughly 
equivalent to 10,000 km / 90 degrees = 111 km, so we're talking around a 
devilish 666 km to the north of Nottingham here as the crow flies.

Lets assume Dishy points itself due south at 59 degrees. The birds are 
at about 550 km. So doing a flat earth approximation for the moment, 
we're having to point at a satellite 550 km up from 660 km away - that 
gives an elevation of about 40 degrees (=arctan(550/660)). Ballpark. Now 
reduce that by the 6 degrees of difference to account for the curvature 
of the earth and we still have around 34 degrees, allowing for a bit of 
leeway either side if the closest bird isn't actually due south but a 
bit to the east or west. Again, ballpark, but we're nowhere near 25 
degrees yet.

So I'd say that should cover it nicely? Where does my envelope err? GEO 
arc protection aside for the moment, of course. And of course just 
because Starlink offers you service doesn't mean that it's actually 
continuous.

On 25/07/2022 8:59 am, Dave Taht via Starlink wrote:
> For those of you that don't follow mike's twitter feed...
>
> https://twitter.com/mikepuchol/status/1551288485713149952 
> <https://twitter.com/mikepuchol/status/1551288485713149952>
>
> -- 
> FQ World Domination pending: 
> https://blog.cerowrt.org/post/state_of_fq_codel/ 
> <https://blog.cerowrt.org/post/state_of_fq_codel>
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink 
> <https://lists.bufferbloat.net/listinfo/starlink>

-- 
****************************************************************
Dr. Ulrich Speidel

School of Computer Science

Room 303S.594 (City Campus)

The University of Auckland
u.speidel@auckland.ac.nz  
http://www.cs.auckland.ac.nz/~ulrich/
****************************************************************



[-- Attachment #2: Type: text/html, Size: 3439 bytes --]

  reply	other threads:[~2022-07-25  8:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-24 20:59 Dave Taht
2022-07-25  8:35 ` Ulrich Speidel [this message]
2022-07-25 21:06   ` Mike Puchol
2022-07-26 13:09     ` Ulrich Speidel
2022-07-26 13:35       ` Mike Puchol
2022-07-27 13:37         ` Ulrich Speidel
2022-07-27 21:02           ` Mike Puchol

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=e3dd7bad-3dae-b64a-97bb-8e2e281c4011@auckland.ac.nz \
    --to=u.speidel@auckland.ac.nz \
    --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