From: Brandon Butterworth <brandon@rd.bbc.co.uk>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: David Lang <david@lang.hm>,
Starlink list <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink no longer available to the Ukrainian army?
Date: Sun, 16 Oct 2022 20:03:50 +0100 [thread overview]
Message-ID: <20221016190349.GA945@sunf68.rd.bbc.co.uk> (raw)
In-Reply-To: <7AFAA1E1-B583-4A42-B188-6D80F9C2DDD5@gmx.de>
On Sun Oct 16, 2022 at 08:44:12PM +0200, Sebastian Moeller via Starlink wrote:
> > and it's worth remembering that it's not just being used for military C&C, it's being used for (almost) all Internet access through the country, normal telcom, Hospitals, community access, etc.
>
> Do we know this for sure? As far as I know (so not very much, one of my
> colleagues in the early 2000s was Ukranian and told me about their figer
> optics telephony system) Ukraine might have some fiber infrastructure
> that should make at least the west not fully reliant on Starlkink.
They have loads of fibre like most countries, there were many reports of
them repairing it after was damage, a few sumarried -
https://www.vice.com/en/article/qjbapv/diy-volunteers-are-repairing-ukraines-destroyed-internet-infrastructure
https://www.forbes.com/sites/thomasbrewster/2022/03/22/while-russians-bombs-fall-around-them-ukraines-engineers-battle-to-keep-the-internet-running/
loads more on twitter.
For c&c and the front line they can't depend on that especially as
they regain areas where Russia has has time to infiltrate/redeploy
the existing infrastructure, and which may now be the target of
their own attack. One of Russias weaknesses was depending on the
local infra for their own operations.
brandon
next prev parent reply other threads:[~2022-10-16 19:03 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
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 [this message]
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=20221016190349.GA945@sunf68.rd.bbc.co.uk \
--to=brandon@rd.bbc.co.uk \
--cc=david@lang.hm \
--cc=moeller0@gmx.de \
--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