Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Daniel AJ Sokolov <daniel@falco.ca>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Re: FCC declares all new router models illegal
Date: Mon, 23 Mar 2026 21:02:14 -0700 (MST)	[thread overview]
Message-ID: <7qrq5oq9-n28o-9q69-5sn5-84r91411qs8n@ynat.uz> (raw)
In-Reply-To: <ffae0fc9-fc8d-4b2a-a04b-42c301e489b9@falco.ca>

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.

and if they ban opensource software, they will ban all routers and a lot of 
other stuff as well.

David Lang

On Mon, 23 Mar 2026, Daniel AJ Sokolov via Starlink wrote:

> Date: Mon, 23 Mar 2026 17:36:17 -0700
> From: Daniel AJ Sokolov via Starlink <starlink@lists.bufferbloat.net>
> Reply-To: Daniel AJ Sokolov <daniel@falco.ca>
> To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
> Subject: [Starlink] FCC declares all new router models illegal
> 
> Dear All,
>
> this may be somewhat off topic, but I think you will all want to know this: 
> Today, the FCC has declared that only routers manufactured in the US may 
> obtain valid FCC certification.
>
> "Production generally includes any major stage of the process through which 
> the device is made, including manufacturing, assembly, design, and 
> development."
>
> I am not aware of any consumer grade router that would be considered made in 
> the US under these rules. Are there any?
>
> Are there any routers that work entirely without open source software?
>
> Previously approved routers are still OK - kind of. The challenge there is 
> that software updates are affected by the new restrictions. The FCC has 
> provided an exemption until March 1, 2027, for certain software updates - 
> after that, who knows.
>
> Manufacturers can apply for exemptions, if - and only if - they have a 
> detailed, time-bound "U.S. Manufacturing and Onshoring Plan", Also, they must 
> disclose competition-sensitive information.
>
> For the official documents, start here:
> https://www.fcc.gov/document/fcc-updates-covered-list-include-foreign-made-consumer-routers
>
> FYI
> Daniel
>
>
> _______________________________________________
> Starlink mailing list -- starlink@lists.bufferbloat.net
> To unsubscribe send an email to starlink-leave@lists.bufferbloat.net
>

  parent reply	other threads:[~2026-03-24  4:02 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 [this message]
2026-03-24  9:58   ` Brandon Butterworth
2026-03-24 22:12     ` David Lang
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=7qrq5oq9-n28o-9q69-5sn5-84r91411qs8n@ynat.uz \
    --to=david@lang.hm \
    --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