Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: "David P. Reed" <dpreed@deepplum.com>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] Starlink deplyment in Ukraine
Date: Sat, 5 Mar 2022 19:39:40 -0500 (EST)	[thread overview]
Message-ID: <1646527180.51036626@apps.rackspace.com> (raw)
In-Reply-To: <mailman.1959.1646493913.1267.starlink@lists.bufferbloat.net>

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


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.
 
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.
 
I'm still appalled by Musk's actions when the Thai boys needed to be rescued from a cave. [ https://www.bbc.com/news/world-us-canada-50667553 ]( https://www.bbc.com/news/world-us-canada-50667553 ) . I hope he learned something when he was sued.
 
 
 
 

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

       reply	other threads:[~2022-03-06  0:39 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 [this message]
2022-03-06  1:02   ` David Lang
2022-03-06  5:58     ` Larry Press
     [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=1646527180.51036626@apps.rackspace.com \
    --to=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