Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Brandon Butterworth <brandon-ml@bogons.net>
Cc: David Lang <david@lang.hm>, Daniel AJ Sokolov <daniel@falco.ca>,
	Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Re: FCC declares all new router models illegal
Date: Tue, 24 Mar 2026 15:12:01 -0700 (MST)	[thread overview]
Message-ID: <0p9ppp3q-n7qr-9sr6-2qq4-p0447p754rop@ynat.uz> (raw)
In-Reply-To: <em19c12da6-54f9-4ba8-8860-1aaf02811ec6@bogons.net>

Brandon Butterworth wrote:

> On 24/03/2026 04:02:14, "David Lang via Starlink" 
> <starlink@lists.bufferbloat.net> wrote:
>> If they are actually banning FCC certification for anything not built in 
>> the US, I don't expect it to last very long, the outcry will just be too 
>> much.
>
> Well, TACO as always.
>
> There are several ways of looking at it.
>
> 1. It's just another shakedown to benefit insiders.
>
> 2. a lever to get manufacturing into USA, devices may remain much
> the same.
>
> 3. defensive as they are considering actions that may cause these
> to become more of a target so they want to be ready - see Viasat
> takedown in 2022.
>
> 4. a way to get NSA blessed devices in to replace other country
> agencies.
>
> Or any combination of these and more.

I actually believe that it's intended as a lever to get manufacturing back into 
the US. But if it actually eliminates all routers, there will be pushback and 
they will back off (at least in implementation timeline)

but while this administration has pushed to move manufacturing back, this would 
be the first time where they have banned all products not manufactured in the US 
in a category (they have banned the government from buying some products from 
outside the US, but not all uses of a category of products by anyone in the US)

which is why I question the breathless reports as being both accurate, and the 
intent

David Lang

  reply	other threads:[~2026-03-24 22:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-24  0:36 [Starlink] FCC declares all new router models illegal Daniel AJ Sokolov
2026-03-24  1:56 ` [Starlink] " David Collier-Brown
2026-03-24  2:01 ` Ulrich Speidel
2026-03-24  2:09   ` Daniel AJ Sokolov
2026-03-24  2:10     ` Ulrich Speidel
2026-03-24  2:20       ` Daniel AJ Sokolov
2026-03-24  3:06   ` Daniel AJ Sokolov
2026-03-24  3:39     ` Inemesit Affia
2026-03-24  4:02 ` David Lang
2026-03-24  9:58   ` Brandon Butterworth
2026-03-24 22:12     ` David Lang [this message]
2026-03-24 23:38       ` Kenneth Porter
2026-03-25  1:00         ` David Lang
     [not found] <177433579052.1741.14062725913348705478@gauss>
2026-03-24 18:10 ` David Fernández

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=0p9ppp3q-n7qr-9sr6-2qq4-p0447p754rop@ynat.uz \
    --to=david@lang.hm \
    --cc=brandon-ml@bogons.net \
    --cc=daniel@falco.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