Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: J Pan <Pan@uvic.ca>
To: Michael Richardson <mcr@sandelman.ca>
Cc: Frantisek Borsik <frantisek.borsik@gmail.com>,
	Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Re: Lost in Space: The Limits of Geolocation in a Satellite-Connected World (new article from Geoff Huston)
Date: Wed, 1 Oct 2025 15:50:15 -0700	[thread overview]
Message-ID: <CAHn=e4j69FhYsS8oOqjFU8JSGBpj6-hpGc_PsjFJ7U-i3cjX1g@mail.gmail.com> (raw)
In-Reply-To: <5880.1759352933@obiwan.sandelman.ca>

it shows up. see http://reddit.com/u/panuvic
--
J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan


On Wed, Oct 1, 2025 at 2:09 PM Michael Richardson <mcr@sandelman.ca> wrote:

> J Pan <Pan@uvic.ca> wrote:
>     > 100.64/10 is starlink's ipv4 access network. from the user side, user
>     > router will get a unique 100.64/10 address on its wan side, and its
>     > cgnat gateway is always fixed at 100.64.0.1. from the user 100.64/10
>     > (100.76.147.112 in my victoria dish example) to 100.64.0.1, it's a
>
> I thought I understood that 100.64.0.1 did not show up in your traceroute
> though?
>
>

  reply	other threads:[~2025-10-01 22:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-01  5:34 [Starlink] " Frantisek Borsik
2025-10-01  5:56 ` [Starlink] " J Pan
2025-10-01 16:46   ` Michael Richardson
2025-10-01 17:40     ` J Pan
2025-10-01 21:08       ` Michael Richardson
2025-10-01 22:50         ` J Pan [this message]
2025-10-01 13:18 ` Livingood, Jason
2025-10-01 21:22   ` David Lang
2025-10-01 21:51     ` Spencer Sevilla
2025-10-01 22:48       ` J Pan
2025-10-01 23:05       ` David Lang
2025-10-02  4:34         ` J Pan
     [not found] ` <22339.1759337017@obiwan.sandelman.ca>
2025-10-01 16:47   ` Michael Richardson
2025-10-01 21:13 ` David Lang

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='CAHn=e4j69FhYsS8oOqjFU8JSGBpj6-hpGc_PsjFJ7U-i3cjX1g@mail.gmail.com' \
    --to=pan@uvic.ca \
    --cc=frantisek.borsik@gmail.com \
    --cc=mcr@sandelman.ca \
    --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