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] "Interesting set of developments with Starlink. Musk says they will support "international aid orgs" in Gaza, Israel now says they will use "all available means" to stop SpaceX from doing so.
Date: Wed, 1 Nov 2023 01:57:46 +1300	[thread overview]
Message-ID: <fda40242-2315-4ca7-9702-c19de7e7161b@auckland.ac.nz> (raw)
In-Reply-To: <108a7588-b12e-4663-a1ba-00b2864a7d90@gmail.com>

On 31/10/2023 2:30 am, Alexandre Petrescu via Starlink wrote:
>
>
> > How they would oppose is a good question - I'm sure the Russians would
> > like to know, too.
> >
> From the public announcements, Russia opposed it (starlink) verbally, 
> only.
>
> I dont think (I did not hear about?) Russia jamming starlink sats.
>
> Russia verbally  once threatened verbally harder the starlink sats, but
> Mr. Musk responded publicly that there are thousands of them up there,
> so it would be hard to imagine putting them all down.  He even said he
> could easily put even more up there.
>
> I did hear about Russia complaining about others jamming their sats.
> Russia persons called the jamming of their sats to be potentially cases
> of war, but they did not repeat that statement later, or I did not
> hear.  I am not sure what in the current legislation made them think so,
> but I would like to know.
>
> I also heard about the VIASAT KA-SAT attack early in the Ukraine
> invasion (it was an attack via Internet, not jamming).
VIASAT are geostationary satellites 36000 km above the Equator, and they 
don't move relative to ground stations like LEO sats (Starlink & Co) do. 
They're a much easier target, both in terms of RF jamming (the further 
you are away from the jammer and your intended transmitter with your 
binoculars, the easier it is to get in front of them) but also in terms 
of damage done - one satellite out equates to service outage to a large 
area. Knock a Starlink sat out and there are another dozen or so within 
sight that Dishy and the bent-pipe teleport can de-camp to, so you'd get 
a few dozens seconds worth of outage at most I guess.
>
> The question would be who has authority over the frequencies above the
> disputed territories.  And it is that authority that would allow, or
> disallow, the use of starlink frequencies (somewhere at 10-15GHz IIRC).
> All Starlink would need to do is request access to that spectrum.
Spectrum access isn't the issue - the spectrum that Starlink uses is 
reserved internationally for space-to-ground and ground-to-space use, 
however they still need a license from the respective government that 
has legislative control over the ground stations in their territory to 
be able to use that spectrum. But that presumes peacetime order. I don't 
think Gaza is awash with radio inspectors checking licences right now.
>
> > Jamming isn't really all that easy (again, ask Russia): To jam
> > Starlink successfully in an area, you'd have to jam the satellites
> > (probably about a dozen most of the time, and changing all the time)
> > from the ground in the same area as the Dishys using them.
> >
> I am interested in the legislation part of that, not the technical.

So which law currently applies in Gaza, and who enforces it? It's 
difficult enough to get a competent radio inspector to turn up at a site 
in some Western countries. In some places, they don't even exist, or 
have no means to investigate off-label use of communication equipment. I 
mentioned Tonga here last year, where marine VHF radio all but replaced 
the domestic wired telephone network for a long time in the northern 
island group of Vava'u, for example.

-- 

****************************************************************
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/
****************************************************************




  parent reply	other threads:[~2023-10-31 12:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-29 16:06 the keyboard of geoff goodfellow
2023-10-29 16:26 ` Dave Taht
2023-10-29 19:10   ` Frantisek Borsik
2023-10-29 19:38   ` Dave Taht
2023-10-30  4:32   ` Joe Hamelin
2023-10-30  5:56     ` Ulrich Speidel
2023-10-30 12:03       ` Alexandre Petrescu
2023-10-30 12:47         ` Ulrich Speidel
2023-10-30 13:30           ` Alexandre Petrescu
2023-10-30 16:49             ` David Lang
2023-10-31 12:57             ` Ulrich Speidel [this message]
2023-10-31 14:26               ` Alexandre Petrescu
2023-11-11  5:09           ` Alexandre Petrescu
2023-11-11 23:47             ` Ulrich Speidel
2023-11-13 10:15               ` Alexandre Petrescu
2023-11-13 16:03                 ` David Lang
2023-11-14  8:48                   ` Alexandre Petrescu
2023-10-30 12:54       ` Alexandre Petrescu
2023-10-30 13:10         ` Ulrich Speidel
2023-10-30 13:39           ` Alexandre Petrescu
2023-10-30  6:02     ` Dave Taht
2023-10-30 17:46   ` Daniel AJ Sokolov
2023-10-30 18:47     ` [Starlink] [off-topic] " Dave Collier-Brown
2023-10-30 18:47     ` [Starlink] " Alexandre Petrescu
2023-10-30 19:58       ` Frantisek Borsik

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=fda40242-2315-4ca7-9702-c19de7e7161b@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