From: Mike Puchol <mike@starlink.sx>
To: starlink@lists.bufferbloat.net, Daniel AJ Sokolov <daniel@falco.ca>
Subject: Re: [Starlink] Starlink for Tonga?
Date: Fri, 18 Feb 2022 08:27:37 +0100 [thread overview]
Message-ID: <866041e1-efaf-43f1-b218-6a6d73f6496f@Spark> (raw)
In-Reply-To: <16b22115-3ec4-cdec-2cb3-ab03d75d9275@falco.ca>
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
Hi Daniel,
I added it after there was a confirmation on Twitter that SpaceX people were on the ground to set one up, and also, as two /27 blocks (IPv4) have been assigned to Fiji’s capital, under the Sydney POP, and they can be pinged.
Wether it’s at the teleport or not, unsure, but for simulation, an error of even a few km doesn’t really matter.
Best,
Mike
On Feb 18, 2022, 06:04 +0100, Daniel AJ Sokolov <daniel@falco.ca>, wrote:
> On 2022-02-07 at 15:29, Mike Puchol wrote:
> > As far as placing a gateway in Fiji, it already has a teleport
> > facility, which will have power and fibre (unless that one has been
> > taken out too?). Checkhttps://goo.gl/maps/6BYXf4R17yys7zNe9
>
> Hey Mike, you put a "SUVA (Emergency)" ground station on starlink.sx.
>
> Is that for simulation, or has Starlink actually installed a ground
> station in Fidschi by now? Would you have positive confirmation?
>
> Thank you
> Daniel
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
[-- Attachment #2: Type: text/html, Size: 1701 bytes --]
next prev parent reply other threads:[~2022-02-18 7:27 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 18:50 Daniel AJ Sokolov
2022-02-07 18:51 ` Nathan Owens
2022-02-07 19:05 ` Christian von der Ropp
2022-02-07 19:06 ` Nathan Owens
2022-02-07 20:38 ` Ulrich Speidel
2022-02-07 20:44 ` Ulrich Speidel
2022-02-10 7:53 ` Ulrich Speidel
2022-02-07 21:18 ` Ben Greear
2022-02-07 21:24 ` David Lang
2022-02-07 21:36 ` Mike Puchol
2022-02-07 22:22 ` Ulrich Speidel
2022-02-07 22:29 ` Mike Puchol
2022-02-07 23:36 ` Ulrich Speidel
2022-02-07 23:47 ` David Lang
2022-02-08 0:20 ` Ulrich Speidel
2022-02-08 1:20 ` David Lang
2022-02-08 4:46 ` Inemesit Affia
2022-02-08 6:25 ` Daniel AJ Sokolov
2022-02-08 7:30 ` Ulrich Speidel
2022-02-08 7:49 ` Daniel AJ Sokolov
2022-02-08 8:22 ` Ulrich Speidel
2022-02-08 8:47 ` Mike Puchol
2022-02-08 8:49 ` Daniel AJ Sokolov
2022-02-08 8:58 ` Mike Puchol
2022-02-08 9:05 ` Daniel AJ Sokolov
2022-02-08 9:10 ` Mike Puchol
2022-02-08 15:22 ` Sebastian Moeller
2022-02-08 10:11 ` Ulrich Speidel
2022-02-08 13:50 ` Christian von der Ropp
2022-02-08 15:28 ` Mike Puchol
2022-02-08 16:25 ` Dave Taht
2022-02-08 18:20 ` Gary E. Miller
2022-02-08 19:12 ` David Lang
2022-02-09 12:09 ` Ulrich Speidel
2022-02-09 19:28 ` [Starlink] Sunburp kills 40 starlink satellites Doc Searls
2022-02-09 19:51 ` Michael Richardson
2022-02-09 12:58 ` [Starlink] Starlink for Tonga? Ulrich Speidel
2022-02-18 5:04 ` Daniel AJ Sokolov
2022-02-18 7:27 ` Mike Puchol [this message]
2022-02-18 9:01 ` Ulrich Speidel
2022-04-19 11:57 ` Mike Puchol
2022-04-19 12:06 ` Dave Taht
2022-04-19 12:43 ` Ulrich Speidel
2022-04-20 1:06 ` Ulrich Speidel
2022-04-20 1:14 ` Jeremy Austin
2022-02-18 10:27 ` Ulrich Speidel
2022-02-18 12:48 ` Rich Brown
2022-02-18 15:43 ` Nathan Owens
2022-02-18 10:29 ` Ulrich Speidel
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=866041e1-efaf-43f1-b218-6a6d73f6496f@Spark \
--to=mike@starlink.sx \
--cc=daniel@falco.ca \
--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