From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: Hayden Simon <h@uber.nz>,
"starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: [Starlink] Re: Starlink and Iran
Date: Fri, 16 Jan 2026 10:06:56 +1300 [thread overview]
Message-ID: <2f37d59d-42f2-4735-a915-50f2b2daf6c0@auckland.ac.nz> (raw)
In-Reply-To: <TYZPR03MB66218EA5930F0571A639BD2DA88CA@TYZPR03MB6621.apcprd03.prod.outlook.com>
On 16/01/2026 9:30 am, Hayden Simon wrote:
> That leaves the most likely alternative as the action occuring from reasonable altitude. Be that in orbit, weather balloon(s)....drones.
>
Not really. Think of a Starlink satellite's beam as a laser pointer
pointing at Dishys on the ground that look at the satellite with a good
old fashioned telescope (which is what the phased array effectively
does). And vice versa (laser pointer at the Dishy, telescope at the
satellite). To disrupt that signal, you have to get yourself in front of
the telescope with your laser pointer so your interfering signal can
even be seen. Getting in front of the telescopes on the ground is
mission impossible because there are a few 10000 of them. Moreover, they
suddenly switch direction to point at another satellite typically every
15 to 75 s (which shorter intervals dominating).
Getting in front of the telescopes on the satellites is somewhat easier
as there are fewer of them and - with a drone - you'd be further away
and they'd already be pointing in your general direction if you're close
to the Dishy you're trying to interfere with. But even so, you'd need
one laser pointer per visible and usable satellite - in each cell you're
wanting to take Starlink out on. Moreover, you wouldn't know whether the
satellite is currently receiving from that cell on a red, blue, or green
light frequency - so you'd have to pump power into all of them. Not trivial.
GPS interference is much easier.
--
****************************************************************
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/
****************************************************************
next prev parent reply other threads:[~2026-01-15 21:07 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <176849731431.1249.14387618908540773471@gauss>
2026-01-15 17:42 ` [Starlink] Re: Starlink and Iran Colin_Higbie
2026-01-15 18:56 ` Jim Forster
2026-01-15 20:15 ` Ulrich Speidel
2026-01-15 20:27 ` Ulrich Speidel
2026-01-15 20:30 ` Hayden Simon
2026-01-15 21:06 ` Ulrich Speidel [this message]
2026-01-15 21:09 ` Hayden Simon
2026-01-15 21:20 ` Ulrich Speidel
2026-01-15 21:23 ` Hayden Simon
[not found] <176851123059.1249.8585659892308012167@gauss>
2026-01-15 21:49 ` Colin_Higbie
2026-01-15 23:15 ` Frantisek Borsik
2026-01-16 0:13 ` Ulrich Speidel
2026-01-16 1:29 ` David Lang
2026-01-16 22:55 ` Frantisek Borsik
2026-01-16 23:06 ` J Pan
[not found] ` <13187.1768590201@obiwan.sandelman.ca>
2026-01-16 23:30 ` Ulrich Speidel
2026-01-17 0:07 ` David Lang
2026-01-17 21:56 ` Ulrich Speidel
2026-01-19 20:39 ` David Lang
2026-01-28 3:09 ` Ulrich Speidel
2026-01-28 3:30 ` David Lang
2026-01-28 4:02 ` Mike Puchol
2026-01-28 9:05 ` Ulrich Speidel
2026-01-28 9:53 ` David Lang
2026-01-28 20:43 ` Ulrich Speidel
2026-01-28 20:55 ` David Lang
2026-01-17 18:32 ` Michael Richardson
2026-01-17 18:38 ` Inemesit Affia
2026-01-17 19:25 ` Michael Richardson
2026-01-17 22:12 ` Ulrich Speidel
2026-01-15 14:50 David Fernández
2026-01-15 16:11 ` Oleg Kutkov
2026-01-15 17:13 ` J Pan
-- strict thread matches above, loose matches on Subject: below --
2026-01-15 9:51 [Starlink] " Ulrich Speidel
2026-01-15 10:06 ` [Starlink] " Inemesit Affia
2026-01-15 10:30 ` Ulrich Speidel
2026-01-15 10:44 ` Inemesit Affia
2026-01-15 11:16 ` Ulrich Speidel
2026-01-15 10:32 ` Inemesit Affia
2026-01-15 10:51 ` Ulrich Speidel
2026-01-15 11:17 ` David Lang
2026-01-15 11:59 ` Sauli Kiviranta
2026-01-15 14:08 ` David Lang
2026-01-15 15:29 ` Sauli Kiviranta
[not found] ` <3af2ac06-e098-4c79-869d-9c389959ca07@gmail.com>
[not found] ` <q9304244-661o-3qsr-o6rp-9q1nqq09r419@ynat.uz>
[not found] ` <4ba64a41-bbbf-4fb5-adb0-c77c15e4ca0f@gmail.com>
2026-01-15 16:20 ` Inemesit Affia
2026-01-15 20:12 ` Ulrich Speidel
2026-01-15 17:10 ` J Pan
2026-01-15 20:07 ` Ulrich Speidel
2026-01-15 21:47 ` Oleg Kutkov
2026-01-16 4:18 ` Ulrich Speidel
2026-01-16 8:12 ` Frantisek Borsik
2026-01-16 8:24 ` Inemesit Affia
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=2f37d59d-42f2-4735-a915-50f2b2daf6c0@auckland.ac.nz \
--to=u.speidel@auckland.ac.nz \
--cc=h@uber.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