Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Darrell Budic <budic@onholyground.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink tidbits from NANOG
Date: Thu, 4 Nov 2021 20:41:53 -0500	[thread overview]
Message-ID: <C6CF1C9B-F0BA-43F0-ACAD-07A85DAF7BF3@onholyground.com> (raw)
In-Reply-To: <CAA93jw6hDodGpCA_hfzH7abk+jAXtnsQ+GR0=r4RO5CJ8H3vgg@mail.gmail.com>



> On Nov 4, 2021, at 11:46 AM, Dave Taht <dave.taht@gmail.com> wrote:
> 
>> - v6 is deliberately not fully functional, but they know some of use are using it and it will eventually be fully activated. May be waiting on the regional connectivity, so will be intersting to see if changes for some areas and not others as they roll it out.
> 
> Deliberate... well, if you ship 10 year old openwrt software to users
> (we'd made a big push for ipv6 there before ipv6 launch day in 2013),
> and
> don't keep up...  I guess you could call that deliberate. I'm pretty
> happy with openwrt 20.2.1. IMHO: ipv6 really requires a modern kernel
> and tools, not less than 4 years old, to deploy well. Maybe there's a
> worthwhile SDR stack, I don't know...
> 

Deliberately not enable radvd in this case, so hopefully easily solvable once they have a v6 backbone they are happy with.

>> - They hate Google's outsourced NOC as much as the rest of us
> 
> Do say more. :) I'm told google at least have a very nice set of tools
> for looking at the characteristics of interchange traffic.

If you’ve ever had to deal with them, it’s a lot of long delays on tickets, no explanation for problems and fix acknowledgements only if you’re lucky, and lots of “please do the needful and revert…” type non-answers. And they never give out data on your traffic once it’s left your box/boundary, even though you’re paying them for the traffic. One of the worst I’ve ever delt with, but fortunately offset by all the smart folk you never get to talk to that ensure most things work really well most of the time.


>> - New ground stations with more capacity are coming (and will be upgrades).
> 
> Would so love universities to get in on some of those. I remember the IMP.

They are emphasizing public peering, so I’m hopefully they’ll keep moving. Many of the university’s already peer at SIX and a couple are at ChIX, so their connectivity will open up a bit. Speaking of, I’ll give a 10G ChIX connection to any public educational institution that wants one and can get to me, so send ‘em my way if they’re in the midwest and interested!

> 
>> - new birds also have 2-3x more ku bandwidth than first gen
> 
> up and down?
> 
> My take on the up problem was that it was regulatory. ?
> 

It’s three beams “up/down” from the Dishys (one at a time in a TDM fashion, which we knew), and one locked on whatever ground station it’s tracking at the moment. Sounded like more capacity on all of them, unclear if it’s better antennas, more power, better tracking, or all of the above. It did sound like the ground stations will get bigger antennas, so that’s probably part of the downlink improvements.

> 
> Just someone telling me under pain of death, "dave, you can't talk for
> X months, but we're going to do cake/fq-codel/pie/something" would be
> comforting. There's a whole internet elsewhere left to fix, starlink
> getting it right and a little publicity around it would do wonders...
> and certainly wifi is highest on my list. As it is, I got annoyed
> enough last week to try and get the autorate sensing code to work well
> on starlink. There's a prototype now that seems to be working well on
> lte, see here: https://forum.openwrt.org/t/cakes-autorate-ingress-testing-needed/108848/186
> 
> Testers wanted.

I’ll get my cake install upgraded and test it out. To be honest, I haven’t even been running it for a while, so they’ve gotten better since you started talking to them even if it isn’t great yet.

> Fixing fixed wireless has been a pain point far, far, far greater
> than the disappointment I felt at starlink so totally missing the
> bufferbloat problem initially. It will take a decade to sort out 5g,
> 4-6 months more for starlink oh! yes! yes! yes!
> 
> More news on that as it happens.
> 
>> - it’s encrypted up and down. I didn’t know that yet, but I may have just missed it.
> 
> I did. But it's really hard to trust that black box and the world has
> otherwise shifted to e2e encryption.

My contact acknowledged that, but it’s nice to know it’s probably better encrypted than the LTE modems we all use everyday already. I imagine we’ll have to continue to depend on the application layer for that sort of e2e encryption, with the advantage that it won’t matter what our transport tech is then.



  parent reply	other threads:[~2021-11-05  1:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04 15:26 Darrell Budic
2021-11-04 16:21 ` Dave Taht
2021-11-04 16:46 ` Dave Taht
2021-11-04 17:11   ` Dave Taht
2021-11-05  1:30     ` Darrell Budic
2021-11-05  1:41   ` Darrell Budic [this message]
2021-11-05  1:46   ` Darrell Budic
2021-11-04 18:16 ` Michael Richardson
2021-11-04 18:25   ` Inemesit Affia
2021-11-04 18:29   ` Dave Taht
2021-11-04 19:10     ` Michael Richardson
2021-11-05  0:34 ` Ulrich Speidel
2021-11-05  1:05   ` Nathan Owens
2021-11-05  1:18     ` Darrell Budic
2021-11-05 22:24       ` Ulrich Speidel
2021-11-05 15:00     ` [Starlink] data sovereignty Michael Richardson
2021-11-05 15:07       ` Spencer Sevilla
2021-11-05 17:36       ` Daniel AJ Sokolov
2021-11-05 18:01       ` Daniel AJ Sokolov
2021-11-05 22:12     ` [Starlink] Starlink tidbits from NANOG Ulrich Speidel
2021-11-05  1:27   ` Darrell Budic
2021-11-05 15:03     ` Michael Richardson

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=C6CF1C9B-F0BA-43F0-ACAD-07A85DAF7BF3@onholyground.com \
    --to=budic@onholyground.com \
    --cc=dave.taht@gmail.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