Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Nick Buraglio <nick@buraglio.com>
To: Starlink@lists.bufferbloat.net
Subject: [Starlink] dhcpv6-pd details
Date: Mon, 17 May 2021 13:58:05 -0500	[thread overview]
Message-ID: <CAGB08_cb8inow-viJ70A6-V8bRu2CuKDR-FtDtjL5ze3DYxQ9A@mail.gmail.com> (raw)

As discussed privately with Dave, I have removed the starlink provided
router and replaced it with a Mikrotik RB2011 to allow for more
granular control, and to better tie into my existing network. This has
allowed me to make a dhcpv6-pd request that is reasonably stable (so
far it has changed once in the last 2 months). The lease time is
incredibly short, which is a little strange but as long as the DHCPv6
server is the same and remains unchanged, it should just hand out the
same prefix upon request.
I also built a very crude measurement display that just uses curl get
and dig via smokeping to display reasonable RTT. It's detailed in the
reddit post here:
https://www.reddit.com/r/Starlink/comments/mykxjv/functional_ipv6_and_some_crude_starlink_latency/
and can be viewed directly here:
https://starmon.qosbox.com/

Making dhcpv6-pd work is pretty standard:

/ipv6 dhcp-client

add add-default-route=yes interface=ether2 pool-name=starlink-ipv6
prefix-hint=::/56 request=prefix

On each interface you want to have IPv6 on:

/ipv6 address

add address=::1 from-pool=starlink-ipv6 interface=bridge.8

add address=::1 from-pool=starlink-ipv6 interface=bridge.6

             reply	other threads:[~2021-05-17 18:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17 18:58 Nick Buraglio [this message]
2021-05-17 19:15 ` Dave Taht
2021-05-17 19:30   ` Nick Buraglio
2021-05-17 19:36     ` David Lang
2021-05-17 19:48       ` Nick Buraglio
2021-05-17 19:59         ` Dave Taht
2021-05-17 21:02           ` Nick Buraglio
2021-05-17 23:56             ` Dave Taht
2021-05-18  2:21               ` Nick Buraglio
2021-05-18  6:51                 ` Gert Doering
2021-05-17 19:37   ` Nathan Owens
2021-05-18  8:33   ` Annika Wickert
2021-05-18 11:37     ` Nick Buraglio
2021-05-18 11:41       ` Annika Wickert
2021-05-18 14:48         ` Nick Buraglio
2021-05-18 14:50           ` Annika Wickert
2021-06-06  3:41             ` Darrell Budic

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=CAGB08_cb8inow-viJ70A6-V8bRu2CuKDR-FtDtjL5ze3DYxQ9A@mail.gmail.com \
    --to=nick@buraglio.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