From: "Mr. Clif" <clif@eugeneweb.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] ch-ch-ch-ch-changes!
Date: Fri, 13 May 2022 09:07:51 -0700 [thread overview]
Message-ID: <29279413-4c9a-0c74-c6db-015f4779765f@eugeneweb.com> (raw)
In-Reply-To: <CAK2MWOvb8w_S=QOOcM_UGx1KKe0bSHDXthJ0WKVrgFhEpVctPQ@mail.gmail.com>
Hi guys,
After waiting for over a year, a couple of weeks ago, our Starlink
terminal finally arrived. The original orders I placed never panned out,
and eventually were canceled, but when I heard about the new service map
feature on the Starlink site, it took all the guess work out of the
order process.
I live in Eugene but had to select some small town near the coast to
place the order. When it arrived, I tried to install the starlink app on
3 (Three) different android devices, but it refused... Grrrr. So I found
some third party Starlink app and tried that, but it would just exit
immediately.
Though the surprising thing is, that when I powered it up in Eugene, it
just worked without the app and despite Eugene not being available for
new service. I also tried it in another town that didn't have service
and it just worked. A couple of days later, we moved it about 50 miles
from the registered service area, also out in the boonies and it's been
working great ever since. Never touched the app, and never turned on
roaming.
Not sure how typical this is.
Ciao,
Clif
On 5/12/22 18:39, Bruce Perens wrote:
> Starlink accepted an order for my address in Berkeley, CA, today. They
> also let me set the location of the Dishy I already have on hand to
> Berkeley, rather than my off-grid location where it hasn't been
> installed yet. That did not work before. However, Dishy has had 14
> minutes to get on the network, and is still doing what it previously
> did - it has 15-second intervals online every 10 minutes or so. I'll
> leave it on and see if it starts working.
>
> Also, my ethernet adapter arrived.
>
> Thanks
>
> Bruce
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2022-05-13 16:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 7:06 [Starlink] Good APNIC blog on Starlink, testing Cubic, Reno, and BBR Bjørn Ivar Teigen
2022-05-06 18:05 ` Dave Taht
2022-05-06 18:28 ` Dave Taht
2022-05-13 1:39 ` [Starlink] ch-ch-ch-ch-changes! Bruce Perens
2022-05-13 2:27 ` David Lang
2022-05-13 16:07 ` Mr. Clif [this message]
2022-05-13 16:09 ` Nathan Owens
2022-05-13 17:28 ` Bruce Perens
2022-05-23 1:51 ` Mr. Clif
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=29279413-4c9a-0c74-c6db-015f4779765f@eugeneweb.com \
--to=clif@eugeneweb.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