Slashdot Mirror
FCC Requires TP-Link To Support Open Source Router Firmware
An anonymous reader writes: Earlier today, the FCC reached a settlement with TP-Link over Wi-Fi router interference. Most of the agreement was routine, addressing compliance with radio emission rules.
But the FCC also did something unprecedented. It required TP-Link to support open source firmware on its routers. You might recall that, last year, the FCC caused a ruckus when it mistakenly suggested it was banning open source router firmware. In fact, the FCC only required that router vendors implement protections for specific radio emission parameters. But the FCC didn't work with router vendors in advance to maintain open source compatibility, resulting in certain vendors (including TP-Link) trying to lock down their routers.
The FCC eventually issued a clarification, but the damage was done. Only recently have a couple router vendors (Linksys and Asus) affirmed that they will continue to support open source firmware.
Today's settlement is a milestone for the FCC. The agency is finally doing something, with deeds and not just words, to demonstrate its support for the open source community. It would be better if the agency hadn't created this mess, but they deserve serious credit for working so hard to fix it.
But the FCC also did something unprecedented. It required TP-Link to support open source firmware on its routers. You might recall that, last year, the FCC caused a ruckus when it mistakenly suggested it was banning open source router firmware. In fact, the FCC only required that router vendors implement protections for specific radio emission parameters. But the FCC didn't work with router vendors in advance to maintain open source compatibility, resulting in certain vendors (including TP-Link) trying to lock down their routers.
The FCC eventually issued a clarification, but the damage was done. Only recently have a couple router vendors (Linksys and Asus) affirmed that they will continue to support open source firmware.
Today's settlement is a milestone for the FCC. The agency is finally doing something, with deeds and not just words, to demonstrate its support for the open source community. It would be better if the agency hadn't created this mess, but they deserve serious credit for working so hard to fix it.
I like my Asus routers. I get very good wifi bandwidth through them and their manufacturer firmware benefits from features being added to its open source codebase.
They're not cheap, but I think they're value for money.
How is such a mandate any better than a ban? A free country should have neither...
It shouldn't be a blanket mandate for all manufacturers, and in this case it isn't for TP-Link either. However, this is part of a larger issue (TP-LINK sold out of compliance routers in violation of FCC rules) and as part of the settlement for that, they agreed to work with the community to allow 3rd party firmware while staying compliant with the new FCC rules, as well as other FCC rules they violated that brought the action in the first place. I'm sure there was some haggling involved and TP-Link probably used this condition to help reduce their fine ($200K as it stands now). It's something I assume the FCC asked for and TP-Link agreed to do as part of the settlement. I'm sure if they said no, the FCC would have settled with them anyway, just probably for a larger fine instead. In this case it's pretty much a win-win-win. TP-Link gets their fine reduced and gets some good publicity out of it, the FCC gets to show that they really didn't mean to ban 3rd party firmware and they get TP-Link in compliance, and the community gets another option for compliant routers they can flash with 3rd party firmware.
I browse on +1 so AC's need not respond, I won't see it.