From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] Re: FCC declares all new router models illegal
Date: Tue, 24 Mar 2026 15:01:23 +1300 [thread overview]
Message-ID: <4fce5ae5-382b-437f-867f-512a2f478a39@auckland.ac.nz> (raw)
In-Reply-To: <ffae0fc9-fc8d-4b2a-a04b-42c301e489b9@falco.ca>
Well it's not entirely off-topic:
https://www.bbc.com/news/articles/c74787w149zo
Quote:
> One exception to the general absence of US-made routers is the newer
> Starlink WiFi router. Starlink is part of Elon Musk's company SpaceX.
>
> The company says the Starlink routers are made in Texas
>
To be frank, I'm not surprised. Ability to infiltrate and interfere with
someone else's network and the resources it harbours is a key advantage
in conflict. I'd be surprised if this wasn't actively exploited at scale
in fact.
On 24/03/2026 1:36 pm, Daniel AJ Sokolov via Starlink wrote:
> 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
--
****************************************************************
Dr. Ulrich Speidel
School of Computer Science
Room 303S.594 (City Campus)
The University of Auckland
u.speidel@auckland.ac.nz
http://www.cs.auckland.ac.nz/~ulrich/
****************************************************************
next prev parent reply other threads:[~2026-03-24 2:01 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 [this message]
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
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=4fce5ae5-382b-437f-867f-512a2f478a39@auckland.ac.nz \
--to=u.speidel@auckland.ac.nz \
--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