FCC Demands TP-Link Support Open Source Third-Party Firmware On Its Routers

from the freedom-to-tinker dept

Last year, we noted how the FCC updated its rules governing routers in the 5 GHz band over safety concerns, stating that some illegally modified router radios operating in the unlicensed bands were interfering with terminal doppler weather radar (TDWR) at airports. The rule changes prohibited tinkering with just the RF capabilities of the devices. But engineers, the EFF, hobbyists and custom-firmware developers feared that because many routers have systems-on-a-chip (SOC) where the radio isn’t fully distinguishable from other hardware — vendors would take the lazy route and block third-party firmware entirely.

That only partially happened.

While the FCC told us explicitly that locking down third-party firmware was not its intent, router manufacturers like TP-Link did indeed take the lazy route — locking down its routers to prevent third-party firmware installs, then blaming the FCC for it. Fortunately other router manufacturers like Belkin/Linksys took the opposite tack, going so far as to use the new rules as a marketing opportunity, highlighting how they’d continue to support tinkerers (at least in regards to its WRT line of routers). Companies like Asus also stated they’d continue supporting the tinkering community.

Fast forward to this week, when the FCC took some interesting steps to try and force TP-Link’s hand on the subject. The regulator announced that it had reached a $200,000 settlement with TP-Link (pdf) for marketing routers to consumers that operated outside of FCC parameters. The FCC’s full consent decree (pdf) offers a bit more detail, noting that TP-Link effectively let some router models be modified to operate outside of accepted U.S. parameters via a toggle setting that let users pretend they lived in other countries, opening the door to potential interference.

Note that this settlement involved routers in the 2.4 GHz band, while the rule changes above governed the 5 GHz band. But in an interesting wrinkle, the FCC used the settlement to push TP-Link back toward supporting open source third-party firmware for 5 GHz devices:

“TP-Link has also agreed to take steps to support innovation in third-party router firmware by committing to investigate security solutions for certain 5 GHz band routers that would permit the use of third-party firmware while meeting the Commission?s security requirements and maintaining the integrity of critical radio parameters.”

The FCC stated the move was an attempt to balance RF safety and interference policy while supporting the freedom to tinker:

“The Commission?s equipment rules strike a careful balance of spurring innovation while protecting against harmful interference,? said Travis LeBlanc, Chief of the Enforcement Bureau. ?While manufacturers of Wi-Fi routers must ensure reasonable safeguards to protect radio parameters, users are otherwise free to customize their routers and we support TP-Link?s commitment to work with the opensource community and Wi-Fi chipset manufacturers to enable third-party firmware on TP-Link routers.”

Note it’s not entirely clear just how hard the FCC will push to ensure TP-Link compliance, and what “steps” TP-Link has to take to return to supporting third-party open source firmware remains a little murky. It’s also likely that other router manufacturers will continue to take the lazy route and shut out tinkerers from installing third-party firmware. Still, it’s a solid signal from the FCC that it at least realizes the value in open source modifications (or the bad PR in hindering it), an increasingly rare position in an era where you often no longer actually own the hardware and devices you buy.

Filed Under: , , , ,
Companies: tp-link

Rate this comment as insightful
Rate this comment as funny
You have rated this comment as insightful
You have rated this comment as funny
Flag this comment as abusive/trolling/spam
You have flagged this comment
The first word has already been claimed
The last word has already been claimed
Insightful Lightbulb icon Funny Laughing icon Abusive/trolling/spam Flag icon Insightful badge Lightbulb icon Funny badge Laughing icon Comments icon

Comments on “FCC Demands TP-Link Support Open Source Third-Party Firmware On Its Routers”

Subscribe: RSS Leave a comment
Anonymous Coward says:

What the heck Techdirt?

I come in here expecting to be depressed, but in stead I get the excact opposite. Was this article posted in error?
What do I do? Should I contact a lawyer? Is it possible to sue for unexpected pleasant emotions?
From what I have read on this site, I would actually stand a pretty good chance of winning.

pixelpusher220 (profile) says:

Why not just in 'restricted zones'?

Why aren’t people who live near airports simply required to buy routers that comply.

If someone lives in flyover country, hundreds of miles from an airport, why are they restricting what routers can be used?

also, see drones and why aren’t the restrictions for airport areas applied to the whole country

Ninja (profile) says:

It’s awesome. Even if the FCC doesn’t really enforce what they asked it is plenty of bad PR to tp-link that may push them and others towards supporting tinkering. Installing some 3rd-party firmware on some routers turn them into beasts for somewhat little money (I’d argue that the companies could learn a thing or two from these initiatives or even just ship the hardware with the option of using their stuff or the most known firmware by default.

Wishful thinking?

Add Your Comment

Your email address will not be published. Required fields are marked *

Have a Techdirt Account? Sign in now. Want one? Register here

Comment Options:

Make this the or (get credits or sign in to see balance) what's this?

What's this?

Techdirt community members with Techdirt Credits can spotlight a comment as either the "First Word" or "Last Word" on a particular comment thread. Credits can be purchased at the Techdirt Insider Shop »

Follow Techdirt

Techdirt Daily Newsletter

Techdirt Deals
Techdirt Insider Discord
The latest chatter on the Techdirt Insider Discord channel...