Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] successful drone attack on starlink terminal
Date: Fri, 23 Feb 2024 14:36:47 +0100	[thread overview]
Message-ID: <b4a9f117-db35-4c9f-8dd6-696eb45ac4e4@gmail.com> (raw)
In-Reply-To: <d59ac7a9-a41f-4ced-978e-701bb514a11b@gmail.com>



Le 23/02/2024 à 14:23, Alexandre Petrescu via Starlink a écrit :
> 
> 
> 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.

A way forward could be to induce equilibrium rather than
instability-increase albeit breakthrough technologies.

More equilibrium might(?) come from suggesting that all starlink be made
equally available to all parties (like Internet is), but that certainly
sounds as a crazy proposal in the current context of sanctions, even if
people do agree that Internet should stay up equally well for all.

So, I dont know.

It's just that it looks very dangerous what is happening there.

Alex

> 
> Alex
> 
>> 
>> 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 
> https://lists.bufferbloat.net/listinfo/starlink

  reply	other threads:[~2024-02-23 13:36 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 [this message]
2024-02-23 18:13   ` Eugene Chang
2024-02-23 18:31     ` Dave Collier-Brown

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=b4a9f117-db35-4c9f-8dd6-696eb45ac4e4@gmail.com \
    --to=alexandre.petrescu@gmail.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