From: Ben Greear <greearb@candelatech.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink deplyment in Ukraine
Date: Mon, 7 Mar 2022 09:34:11 -0800 [thread overview]
Message-ID: <c7d20d3b-1e90-2524-e192-eb047a3fcd2a@candelatech.com> (raw)
In-Reply-To: <1646601019.667431004@apps.rackspace.com>
On 3/6/22 1:10 PM, David P. Reed wrote:
> Very interesting info about where current ground stations are, but of course Kyiv, Lviv, Kharkiv are close to some adjacent countries that already have Starlink
> ground stations (didn't know they were up and running in Turkey).
>
> Regarding ground-level repeating, the radio horizon is very short except in VHF where you can in principle bounce off the ionosphere. Don't join the Flat Earth
> Society, the earth isn't very flat at all.
>
> (yes, some small bands actually bend around the earth in the Troposhere, but bitrates feasible in that bandwidth is very poor. Maybe voice grade)
>
> Microwave multihop links require LOS and except from mountaintop to mountaintop, it's hard to maintain them cheaply - Wall St uses microwaves between NYC and
> Chicago, because the latency is much lower number of microseconds than direct fiber would be (little known fact about the difference between speed of light in
> glass vs. air).
>
> These technologies are "off the shelf" for fixed wireless deployment, but if I were trying to maintain or build a quick replacement for existing cables using
> wireless, I suspect it would largely be too little, too late.
For email, and anything else that can be stored and forwarded, you should be able to zig-zag from ground to sky to ground,
but it would take specialized software setup on the ground intermediate hops (something like bittorrent and/or an email
proxy I guess), and it would require the sky to be able to hair-pin ground-to-ground. So, a bit of work, but hopefully is
software-only fix.
For instance: Ground-east-1 <-> sky-to-the-west <-> ground-middle <-> sky-more-to-the-west <-> internet-ground-station-to-the-west
And maybe it is not directly due west due to orbital mechanics, but I think you get the idea.
Latency would be in minutes or maybe hours, but that is still a lot better than nothing.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2022-03-07 17:34 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
[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 [this message]
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=c7d20d3b-1e90-2524-e192-eb047a3fcd2a@candelatech.com \
--to=greearb@candelatech.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