From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: Jonathan Bennett <jonathanbennett@hackaday.com>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] insanely great waveform result for starlink
Date: Sat, 14 Jan 2023 11:51:01 +1300 [thread overview]
Message-ID: <153228f4-c659-dfb3-8a71-aa8912e1f17a@auckland.ac.nz> (raw)
In-Reply-To: <CAHtUBuhk=V5Eff5P-gkx1s2W3tzL8eFZ711yWb+wvdqBbJ=fcw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2754 bytes --]
On 14/01/2023 6:02 am, Jonathan Bennett wrote:
>
> It'd be interesting to hear from Jonathan what the availability of
> home
> broadband is like in the Dallas area. I note that it's at a lower
> latitude (33N) than Auckland, but the difference isn't huge. I notice
> two teleports each about 160 km away, which is also not too bad. I
> also
> note Starlink availability in the area is restricted at the moment -
> oversubscribed? But if Jonathan gets good data rates, then that means
> that competition for bird capacity can't be too bad - for whatever
> reason.
>
> I'm in Southwest Oklahoma, but Dallas is the nearby Starlink gateway.
> In cities, like Dallas, and Lawton where I live, there are good
> broadband options. But there are also many people that live outside
> cities, and the options are much worse. The low density userbase in
> rural Oklahoma and Texas is probably ideal conditions for Starlink.
Ah. So what actually happens here is that you're relatively close to the
Springer teleport (~120 km), and the IP address that Starlink assigns to
you gets geolocated to Dallas. Given lack of current Starlink
availability in the region that isn't correlating with population
density like in other parts of the US, we're probably talking lots of
satellite capacity for very few users here. Plus the extra fibre latency
down to Dallas is peanuts. Which explains your data. You're at
34-something north, which is not that different from Auckland.
> Clear view of the sky is king for Starlink reliability. I've got my
> dishy mounted on the back fence, looking up over an empty field, so
> it's pretty much best-case scenario here.
So-so. Your dishy probably orients itself north-facing, but you'll still
be talking via your closest teleport or teleports, so Springer or Dumas.
If Starlink can talk to satellites that are straight overhead, it will -
I've attached a photo of my current setup at home, dishy south-facing
onto my roof. I've pinged for almost a day now in this configuration and
have < 1% loss. Practically all loss events are one-offs, i.e., outages
are under 2 s.
Before that, I had the dishy on the ground in the same position, and had
around 2% ping loss. So being able to see more of the sky makes a bit of
a difference obviously, but it's not huge. Internet was "usable" in both
configurations.
--
****************************************************************
Dr. Ulrich Speidel
School of Computer Science
Room 303S.594 (City Campus)
The University of Auckland
u.speidel@auckland.ac.nz
http://www.cs.auckland.ac.nz/~ulrich/
****************************************************************
[-- Attachment #1.2: Type: text/html, Size: 4137 bytes --]
[-- Attachment #2: 20230114_074033.jpg --]
[-- Type: image/*, Size: 4480431 bytes --]
prev parent reply other threads:[~2023-01-13 22:51 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 17:26 [Starlink] the grinch meets cloudflare's christmas present Dave Taht
2023-01-04 19:20 ` [Starlink] [Rpm] " jf
2023-01-04 20:02 ` rjmcmahon
2023-01-04 21:16 ` Ulrich Speidel
2023-01-04 23:54 ` Bruce Perens
2023-01-05 2:48 ` Dave Collier-Brown
2023-01-05 3:11 ` Dick Roy
2023-01-05 11:25 ` Sebastian Moeller
2023-01-06 0:01 ` Dick Roy
2023-01-06 9:43 ` Sebastian Moeller
2023-01-05 6:11 ` rjmcmahon
2023-01-05 11:11 ` [Starlink] [Bloat] " Sebastian Moeller
2023-01-06 16:38 ` [Starlink] [LibreQoS] " MORTON JR., AL
2023-01-06 20:38 ` [Starlink] [Rpm] " rjmcmahon
2023-01-06 20:47 ` rjmcmahon
[not found] ` <89D796E75967416B9723211C183A8396@SRA6>
[not found] ` <a082b2436e6ba7892d2de8e0dfcc5acd@rjmcmahon.com>
[not found] ` <3696AEA5409D4303ABCBC439727A5E40@SRA6>
[not found] ` <CAKJdXWBb0VxSSoGAQTe3BXFLXCHd6NSspRnXd1frK2f66SLiUw@mail.gmail.com>
[not found] ` <CAA93jw6B_9-WE9EEFuac+FAH-2dcULk=_3i_HfhCSVSOxyM7Eg@mail.gmail.com>
[not found] ` <CA+Ld8r8hR8KF35Yv7A3hb1QvC9v9ka2Nh2J=HEm0XhPfvAAcag@mail.gmail.com>
[not found] ` <CAKJdXWC+aEy1b3vB-FFd+tnfT+Ni5O9bZ+p4kkhj-FzMPVGGcQ@mail.gmail.com>
[not found] ` <CAA93jw4DcBhA8CevRQoMbzjO-3Jt+emr+xvnJ-hUGkT+n0KJzg@mail.gmail.com>
[not found] ` <CH0PR02MB79800FF2E40CE037D6802D71D3FD9@CH0PR02MB7980.namprd02.prod.outlook.com>
[not found] ` <CAKJdXWDOFbzsam2C_24e9DLkc18ed4uhV51hOKVjDipk1Uhc2g@mail.gmail.com>
2023-01-13 4:08 ` [Starlink] insanely great waveform result for starlink Dave Taht
2023-01-13 4:26 ` Jonathan Bennett
2023-01-13 5:13 ` Ulrich Speidel
2023-01-13 5:25 ` Dave Taht
2023-01-13 12:27 ` Ulrich Speidel
2023-01-13 17:02 ` Jonathan Bennett
2023-01-13 17:26 ` Dave Taht
2023-01-13 17:41 ` Jonathan Bennett
2023-01-13 18:09 ` Nathan Owens
2023-01-13 20:30 ` Nathan Owens
2023-01-13 20:37 ` Dave Taht
2023-01-13 21:24 ` Nathan Owens
2023-01-13 20:49 ` Dave Taht
2023-01-13 21:25 ` Luis A. Cornejo
2023-01-13 21:30 ` Nathan Owens
2023-01-13 22:09 ` Jonathan Bennett
2023-01-13 22:30 ` Luis A. Cornejo
2023-01-13 22:32 ` Dave Taht
2023-01-13 22:36 ` Luis A. Cornejo
2023-01-13 22:42 ` Jonathan Bennett
2023-01-13 22:49 ` Dave Taht
2023-01-13 23:44 ` Dave Taht
[not found] ` <CALjsLJv5cbfHfkxqHnbjxoVHczspYvxc_jrshzs1CpHLEDWyew@mail.gmail.com>
2023-01-14 14:20 ` Nathan Owens
2023-01-14 15:53 ` Dave Taht
2023-01-14 16:33 ` Dave Taht
2023-01-14 15:52 ` Dave Taht
2023-01-13 20:25 ` Pat Jensen
2023-01-13 20:40 ` Dave Taht
2023-01-13 22:51 ` Ulrich Speidel [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=153228f4-c659-dfb3-8a71-aa8912e1f17a@auckland.ac.nz \
--to=u.speidel@auckland.ac.nz \
--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