Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Mike Puchol <mike@starlink.sx>
To: starlink@lists.bufferbloat.net
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink no longer available to the Ukrainian army?
Date: Fri, 14 Oct 2022 16:17:45 +0200	[thread overview]
Message-ID: <bfacf8a6-1292-4d63-91db-6e2fdd0b92d9@Spark> (raw)
In-Reply-To: <r620q243-6nss-p5o3-7p2o-r980q0847009@ynat.uz>

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

Juliusz, see the Twitter thread I linked to, it explains precisely the jamming scenarios they could be facing, and how they are possible.

Best,

Mike
On Oct 14, 2022 at 15:11 +0200, David Lang via Starlink <starlink@lists.bufferbloat.net>, wrote:
> satellites are visible from a wide area, and if you are talking about jamming
> the Ukrainian Army, they are going to be close enough to affect ground stations
> as well.
>
> On Fri, 14 Oct 2022, Juliusz Chroboczek wrote:
>
> > > you need to provide the rest of the information, namely that Russia is
> > > actively jamming communications.
> >
> > Interesting, I wasn't aware that they have the capability to do that in
> > areas that they do not control. Do you have any further information?
> >
> > -- Juliusz
> >
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink

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

  reply	other threads:[~2022-10-14 14:18 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 12:06 Juliusz Chroboczek
2022-10-14 12:45 ` David Lang
2022-10-14 13:05   ` Juliusz Chroboczek
2022-10-14 13:11     ` David Lang
2022-10-14 14:17       ` Mike Puchol [this message]
2022-10-14 18:26         ` Juliusz Chroboczek
2022-10-14 20:44           ` Mike Puchol
2022-10-16 17:31             ` Steve Stroh
2022-10-16 17:56               ` Dave Taht
2022-10-16 18:28               ` Vint Cerf
2022-10-14 12:51 ` Mike Puchol
2022-10-14 13:13   ` Juliusz Chroboczek
2022-10-14 14:15     ` Mike Puchol
2022-10-14 16:05       ` Juliusz Chroboczek
2022-10-14 17:13         ` Kurtis Heimerl
2022-10-14 17:28           ` David Lang
2022-10-14 18:16             ` Juliusz Chroboczek
2022-10-14 18:32             ` Larry Press
2022-10-14 19:32               ` Benjamin Henrion
2022-10-14 19:35               ` David Lang
2022-10-14 20:07                 ` David Lang
2022-10-14 22:29                   ` Dave Taht
2022-10-15 16:51                   ` Larry Press
2022-10-16  6:42                     ` Sebastian Moeller
2022-10-16  8:45                       ` Bruce Perens
2022-10-16 16:31                         ` Dave Taht
2022-10-16 17:00                           ` Sebastian Moeller
2022-10-16 19:55                           ` Brandon Butterworth
2022-10-16 20:25                           ` Bruce Perens
2022-11-02  3:50                             ` [Starlink] 25 years of open source - where we went wrong, and how to fix it Dave Taht
2022-10-14 19:13             ` [Starlink] Starlink no longer available to the Ukrainian army? tom
2022-10-14 19:41               ` David Lang
2022-10-14 20:09                 ` Dave Taht
2022-10-16 17:50                 ` Steve Stroh
2022-10-16 17:57                   ` Nathan Owens
2022-10-16 18:01                     ` Dave Taht
2022-10-16 18:29                       ` Vint Cerf
2022-10-16 18:33                         ` David Lang
2022-10-16 18:44                           ` Sebastian Moeller
2022-10-16 19:03                             ` Brandon Butterworth
2022-10-16 19:37                               ` Ulrich Speidel
2022-10-16 19:51                             ` David Lang
2022-10-16 20:37                               ` Michael Richardson
2022-10-16 20:52                                 ` Bruce Perens
2022-10-16 22:17                                 ` Brandon Butterworth

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=bfacf8a6-1292-4d63-91db-6e2fdd0b92d9@Spark \
    --to=mike@starlink.sx \
    --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