Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <davet@teklibre.net>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] ipv4 address space?
Date: Fri, 11 Jun 2021 06:52:24 -0700	[thread overview]
Message-ID: <56A85B08-2E65-4165-B4B4-BA0927122781@teklibre.net> (raw)

I am of course happy that with a real OS (linux/pfsense/openwrt) in front of the dishy that an dhcpv6-pd ipv6/56 can be had.

… frustrated that the lease time is only 5 minutes and changes sometimes in under 24 hrs. Most OSes still don’t handle an ipv6 retraction all that well, and only apps like “mosh” can stay nailed up when the underlying ips change.

while we’ve had ipv6 “source specific routing" and “bcp38" working in openwrt for 7+ years now, I doubt that’s working anywhere else.

I got two questions:

1) How much ipv4 address space does starlink actually have? (and how tight is the market nowadays?) 

2) how often does the external ipv4 address change?

             reply	other threads:[~2021-06-11 13:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11 13:52 Dave Taht [this message]
2021-06-11 14:01 ` Nathan Owens
2021-06-11 14:44 ` Gert Doering

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=56A85B08-2E65-4165-B4B4-BA0927122781@teklibre.net \
    --to=davet@teklibre.net \
    --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