From: David Lang <david@lang.hm>
To: Jonathan Bennett <jonathanbennett@hackaday.com>
Cc: starlink@lists.bufferbloat.net, Dave Taht <dave.taht@gmail.com>
Subject: Re: [Starlink] Starlink Roaming
Date: Mon, 14 Feb 2022 12:29:08 -0800 (PST) [thread overview]
Message-ID: <1p492142-q944-r494-6s6r-p6q37s57qnq4@ynat.uz> (raw)
In-Reply-To: <CAHtUBuhrNzcjucBFguo=YfHsnVcoFR0DDcwBkPGaK8P1cZ7+7Q@mail.gmail.com>
I asked starlink about temp service away from my registered location, they said
I have two options
1. formally change the service location (if approved, guaranteed to work, but
you aren't guaranteed to be able to change the service location back)
2. best effort, set it up and try it. Service may perfect, or may be worse (all
the way to non-existant) depending on how many other dishes are in use in the
area.
I've done some limited testing with my dish within about 15 miles of my
registered location (in both cases with less than optimal sky views) and it's
worked without a hitch. I plan to do a test further away this weekend (but in a
less populated area, so I have high hopes)
David Lang
On Mon, 14 Feb 2022, Jonathan Bennett wrote:
> It appears that there is now a system in place for Starlink to re-connect
> even if you are outside your official service cell. For those of us who
> want to use Starlink on vacations or other trips, this is quite the
> development.
>
> --Jonathan Bennett
>
next prev parent reply other threads:[~2022-02-14 20:29 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 19:53 Jonathan Bennett
2022-02-14 20:29 ` David Lang [this message]
2022-02-14 21:43 ` Mike Puchol
2022-02-14 21:53 ` Jonathan Bennett
2022-02-14 21:59 ` Mike Puchol
2022-02-21 7:22 ` Larry Press
2022-02-21 7:29 ` David Lang
2022-02-21 20:31 ` Dick Roy
2022-02-21 20:43 ` Mike Puchol
2022-02-21 20:52 ` David Lang
2022-02-21 21:17 ` Dick Roy
2022-02-21 21:32 ` David Lang
2022-02-21 21:58 ` Nathan Owens
2022-02-21 22:26 ` Dick Roy
2022-02-21 23:08 ` Steve Golson
2022-02-21 23:15 ` Nathan Owens
2022-02-22 1:19 ` Dick Roy
2022-02-21 22:02 ` Daniel AJ Sokolov
2022-02-22 2:17 ` David Lang
2022-02-22 5:34 ` Mike Puchol
2022-02-22 7:20 ` Dick Roy
2022-02-22 7:42 ` Mike Puchol
2022-02-22 7:51 ` Dick Roy
2022-02-22 9:03 ` Sebastian Moeller
2022-02-22 9:40 ` Mike Puchol
2022-02-22 9:46 ` Sebastian Moeller
2022-02-22 10:01 ` Mike Puchol
2022-02-22 10:37 ` Vint Cerf
2022-02-22 11:14 ` Mike Puchol
2022-02-22 7:58 ` Ulrich Speidel
2022-02-22 8:51 ` David Lang
2022-02-22 7:47 ` Dick Roy
2022-02-22 8:55 ` David Lang
2022-02-22 23:14 ` Dick Roy
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=1p492142-q944-r494-6s6r-p6q37s57qnq4@ynat.uz \
--to=david@lang.hm \
--cc=dave.taht@gmail.com \
--cc=jonathanbennett@hackaday.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