From: Larry Press <lpress@csudh.edu>
To: David Lang <david@lang.hm>, "David P. Reed" <dpreed@deepplum.com>
Cc: "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink deplyment in Ukraine
Date: Sun, 6 Mar 2022 05:58:41 +0000 [thread overview]
Message-ID: <BYAPR03MB38636126A57966F48EFA05BEC2079@BYAPR03MB3863.namprd03.prod.outlook.com> (raw)
In-Reply-To: <opq1rqp-ppsr-85ss-2po2-338rs949or8@ynat.uz>
[-- Attachment #1: Type: text/plain, Size: 4244 bytes --]
Ground stations in Turkey, Lithuania, and Poland are reachable from Kyiv. https://circleid.com/posts/20220301-spacex-starlink-service-in-ukraine-is-an-important-government-asset. The one in Turkey is often out of range.
________________________________
From: Starlink <starlink-bounces@lists.bufferbloat.net> on behalf of David Lang <david@lang.hm>
Sent: Saturday, March 5, 2022 5:02 PM
To: David P. Reed <dpreed@deepplum.com>
Cc: starlink@lists.bufferbloat.net <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink deplyment in Ukraine
On Sat, 5 Mar 2022, David P. Reed wrote:
> THis is a good discussion, and I hope for more.
>
> 1. I'm really curious how well Starlink's bent-pipe architecture actually
> works in a context like Ukraine where fiber and copper infrastructure are
> vulnerable and less redundant than in a place like the UK. I'm not so worried
> about the dishy's working or being targeted. They can be moved and disguised.
> What is not being discussed here (or anywhere) is where the ground stations
> that the traffic must *all* traverse are, and the fact that they are Single
> Points of Failure, and must be nailed down in places which are close enough to
> the dishy they serve, and also fiber-backhauled into the Internet. This is a
> serious technical issue that interests me, mostly because Starlink doesn't
> publish its technical specs.
>
> So these ground stations for Ukrainian coverage are where? Ukraine is a BIG
> area. It certainly won't be covered by one ground station. And it certainly
> can't be just an 18-wheeler with a huge antenna on top, because it needs to be
> connected to a point-of-presence with lots of capacity - the sum of all the
> dishy's peak loads.
>
> I'm suspecting that some ground station is actually in Ukraine itself, but
> putting it in Kyiv just makes it a tempting target (like a power station or
> water utility), and it is much more vulnerable and visible to Russian troops
> in the area.
>
> Now Poland and Moldova are potential sites that might cover part of Ukraine,
> but certainly not that far into the country.
I actually doubt that the ground stations are in Ukraine, that would require
much more significant setup (think about the engineers flown out to installa
ground station to support Tonga) and would be extremely vulnerable to
disruption.
Remember, service was turned on and dishys delivered in < 48 hours.
disrupting the ground stations in adjacent countries is a rather significant
escalation.
We don't know the full reach of a ground station, but I suspect that some of the
limitations that people have been talking about are as much software/regulations
as RF/hardware, and I would not be surprised if such restritions are being
relaxed a bit there.
> 2. I hope that Starlink isn't just doing this to get Musk in the news, but
> actually wants to facilitate ongoing connectivity to the Internet, independent
> of "sides". (as others here have noted, communications control is a very
> imprecise instrument when it is a tool of aggression - "virtue signalling" by
> a billionaire who has been knowmid 1990's trying to bring Internet
> connectivity to poor people in Jamaica and poro people in the West Bank each
> partly caused the deaths of a few people we thought we were only helping. But
> that's a long story in each context).
>
> More seriously, if Musk is not covering much of Ukraine at all, and just
> shipping dishy's there, that's good, but I hope he doesn't try to take credit
> for more than Starlink actually can do. I mean it would also be nice if
> Mikrotik shipped in meshable WiFi, but that's of limited utility, even if the
> most clever hackers tried to create an outdoor mesh of them. The coverage
> would be very limited, and you still need a non-WiFi path to the Internet to
> communicate over wide areas.
So far he has not said anything about the use of them, although some people in
Ukraine had said they have them and are prepared to use them when the wired
Internet is disrupted. I would not expect to hear that much about people using
them in remote areas yet. We'll probably hear more about that weeks to months
later.
David Lang
[-- Attachment #2: Type: text/html, Size: 5795 bytes --]
next prev parent reply other threads:[~2022-03-06 5:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1959.1646493913.1267.starlink@lists.bufferbloat.net>
2022-03-06 0:39 ` David P. Reed
2022-03-06 1:02 ` David Lang
2022-03-06 5:58 ` Larry Press [this message]
[not found] ` <BYAPR03MB38636126A57966F48EFA05BEC2079@BYAPR03MB3863.namprd03.prod.outloo k.com>
[not found] ` <BYAPR03MB38636126A57966F48EFA05BEC2079@BYAPR03MB3863.namprd03.prod.outlook. com>
2022-03-06 21:10 ` David P. Reed
2022-03-06 21:17 ` David Lang
2022-03-07 17:34 ` Ben Greear
2022-03-07 17:49 ` Sebastian Moeller
2022-03-06 3:01 ` Michael Richardson
2022-03-08 6:01 ` 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=BYAPR03MB38636126A57966F48EFA05BEC2079@BYAPR03MB3863.namprd03.prod.outlook.com \
--to=lpress@csudh.edu \
--cc=david@lang.hm \
--cc=dpreed@deepplum.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