Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Collier-Brown <dave.collier-Brown@indexexchange.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] successful drone attack on starlink terminal
Date: Fri, 23 Feb 2024 13:31:08 -0500	[thread overview]
Message-ID: <7d66a42e-7a40-4187-8bb4-4fe5c979ad64@indexexchange.com> (raw)
In-Reply-To: <7B90FA63-4941-4929-A850-65742AE8E09F@alum.mit.edu>

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

When I was in  the reserves (in an era of dinosaurs and stone axes), the regulars were using encrypted, frequency-agile radios. They were hard to localize unless you were so close that they were the loudest thing on the airwaves.

Using Starlink from a fixed location Could Be Bad.

--dave

On 2024-02-23 13:13, Eugene Chang via Starlink wrote:




On Feb 23, 2024, at 3:23 AM, Alexandre Petrescu via Starlink <starlink@lists.bufferbloat.net><mailto:starlink@lists.bufferbloat.net> wrote:



Le 23/02/2024 à 13:04, Dave Taht via Starlink a écrit :


https://twitter.com/Megaconstellati/status/1760996758363029734
In general, two can play at this game, and given the low cost and good
range, and relative ease of building a sensor for the starlink
frequencies, I see starlinks fading from the battlefield. For that
matter, nearly every form of electronic communication, be it wifi, or
5G. Fiber or laser will be used instead.



But laser could be blinded by counter-lasers, fiber could be cut by scissors, etc.

Measures, counter-measures, counter-counter-measures and so on, equally well on each of these media.

Alex



The point is some media can be remotely detected and targeted.

Laser is harder to detect than wireless (radio).
Fiber is even harder to be detected remotely.

Gene







See also the flipper zero.
https://arstechnica.com/security/2024/02/canada-vows-to-ban-flipper-zero-device-in-crackdown-on-car-theft/


_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net<mailto:Starlink@lists.bufferbloat.net>
https://lists.bufferbloat.net/listinfo/starlink







_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net<mailto:Starlink@lists.bufferbloat.net>
https://lists.bufferbloat.net/listinfo/starlink


--
David Collier-Brown,         | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
dave.collier-brown@indexexchange.com<mailto:dave.collier-brown@indexexchange.com> |              -- Mark Twain


CONFIDENTIALITY NOTICE AND DISCLAIMER : This telecommunication, including any and all attachments, contains confidential information intended only for the person(s) to whom it is addressed. Any dissemination, distribution, copying or disclosure is strictly prohibited and is not a waiver of confidentiality. If you have received this telecommunication in error, please notify the sender immediately by return electronic mail and delete the message from your inbox and deleted items folders. This telecommunication does not constitute an express or implied agreement to conduct transactions by electronic means, nor does it constitute a contract offer, a contract amendment or an acceptance of a contract offer. Contract terms contained in this telecommunication are subject to legal review and the completion of formal documentation and are not binding until same is confirmed in writing and has been signed by an authorized signatory.

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

      reply	other threads:[~2024-02-23 18:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23 12:04 Dave Taht
2024-02-23 13:23 ` Alexandre Petrescu
2024-02-23 13:36   ` Alexandre Petrescu
2024-02-23 18:13   ` Eugene Chang
2024-02-23 18:31     ` Dave Collier-Brown [this message]

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=7d66a42e-7a40-4187-8bb4-4fe5c979ad64@indexexchange.com \
    --to=dave.collier-brown@indexexchange.com \
    --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