Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: "Mr. Clif" <clif@eugeneweb.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] ch-ch-ch-ch-changes!
Date: Sun, 22 May 2022 18:51:07 -0700	[thread overview]
Message-ID: <f67267de-e9cb-b554-9624-52a5e2b02d2b@eugeneweb.com> (raw)
In-Reply-To: <CAK2MWOvDfcOV-HC=BZeAVxAnE5nwtFgaEDGuZZ0qS2nVmKk=Qw@mail.gmail.com>

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

Say, does anyone have an idea as to how many terminals will be out at 
burning man and the likelihood that we'll all get service? :-)

     Clif

On 5/13/22 10:28, Bruce Perens wrote:
> Our Starlink came on in Berkeley after a half hour or so. 
> Unfortunately there are too many trees around its present location, so 
> it will be moving to my off-grid site and no Starlink at home for now.
>
>     Thanks
>
>     Bruce
>
> On Fri, May 13, 2022 at 9:09 AM Nathan Owens <nathan@nathan.io> wrote:
>
>     It will presumably work for now, but if you have "roaming: True"
>     in the gRPC data, you'll likely have to pay another $25/mo for
>     Portability, and accept slower/degraded service.
>
>     On Fri, May 13, 2022 at 9:07 AM Mr. Clif <clif@eugeneweb.com> wrote:
>
>         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
>
>         _______________________________________________
>         Starlink mailing list
>         Starlink@lists.bufferbloat.net
>         https://lists.bufferbloat.net/listinfo/starlink
>
>     _______________________________________________
>     Starlink mailing list
>     Starlink@lists.bufferbloat.net
>     https://lists.bufferbloat.net/listinfo/starlink
>
>
>
> -- 
> Bruce Perens K6BP

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

      reply	other threads:[~2022-05-23  1:51 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
2022-05-13 16:09     ` Nathan Owens
2022-05-13 17:28       ` Bruce Perens
2022-05-23  1:51         ` Mr. Clif [this message]

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=f67267de-e9cb-b554-9624-52a5e2b02d2b@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