Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <davet@teklibre.net>
To: Nathan Owens <nathan@nathan.io>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Anycast on a Shoestring
Date: Tue, 15 Jun 2021 11:36:36 -0700	[thread overview]
Message-ID: <C7523507-37E8-497B-8F9F-1EEFBD67709C@teklibre.net> (raw)
In-Reply-To: <CALjsLJu24BGOyUyYRMHMz=tnKcL4GNAVyGdfbvHzG4ELTCL=iA@mail.gmail.com>

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



> On Jun 14, 2021, at 8:02 AM, Nathan Owens <nathan@nathan.io> wrote:
> 
> https://ripe69.ripe.net/presentations/36-Anycast-on-a-shoe-string-RIPE69.pdf <https://ripe69.ripe.net/presentations/36-Anycast-on-a-shoe-string-RIPE69.pdf>
very cool. I pinged him via twitter.

It so happens I have a pair of spare /23s at the moment. Trying to get back control of one of my old BGP AS numbers though has been a bear. I hate to give up on its 16 bit glory. 

One of the use cases for the high res irtt-based cosmic background bufferbloat detector was to find route flaps in the core of the internet. 

Paris traceroute is helpful also.

> 
> How to build a cheap anycast setup 
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink


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

  reply	other threads:[~2021-06-15 19:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-14 15:02 Nathan Owens
2021-06-15 18:36 ` Dave Taht [this message]
2021-06-15 19:08   ` Jared Mauch

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=C7523507-37E8-497B-8F9F-1EEFBD67709C@teklibre.net \
    --to=davet@teklibre.net \
    --cc=nathan@nathan.io \
    --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