Wi-Fi Hobbyists Worry New FCC Rules Could Ban Custom Firmware A new FCC Notice of Proposed Rule Making (NPRM) has some worried that new FCC rules could prohibit modification of routers with third party firmware like OpenWRT. According to the NPRM in question (pdf), the FCC says it's looking to modify equipment authorization rules to ensure that RF devices operating in the United States do not cause harmful interference, and has been fielding public comment since the rules were proposed last year.

But one specific portion of the new proposal raised the hackles of some Wi-Fi enthusiasts at the recent BattleMesh 8 event , who claimed that the FCC could (intentionally or otherwise) put the kibosh on third-party firmware. Digging into the rules, it's the specific wording of 15.407i that has some worried the FCC could restrict custom firmware: quote: Manufacturers must implement security features in any digitally modulated devices capable of operating in any of the U-NII bands, so that third parties are not able to reprogram the device to operate outside the parameters for which the device was certified. The software must prevent the user from operating the transmitter with operating frequencies, output power, modulation types or other radio frequency parameters outside those that were approved for the device. Manufacturers may use means including, but not limited to the use of a private network that allows only authenticated users to download software, electronic signatures in software or coding in hardware that is decoded by software to verify that new software can be legally loaded into a device to meet these requirements and must describe the methods in their application for equipment authorization. The rules also require that hardware vendors must "describe in detail how the device is protected from 'flashing' and the installation of third-party firmware such as DD-WRT." The rules also require that hardware vendors must "describe in detail how the device is protected from 'flashing' and the installation of third-party firmware such as DD-WRT." However, others argue that the FCC has worded their proposal poorly, is solely focused in preventing modification to specific aspects of the radios themselves, and isn't really interested in locking down the installation of third-party software. Indeed, it would be out of character for FCC boss Tom Wheeler -- the first FCC boss in fifteen years to truly support net neutrality -- to suddenly think it's a good idea to prohibit custom firmware installation on owned hardware. I've reached out to the FCC for comment. Those concerned have until August 16 to share their thoughts with the FCC on the proposed rule changes. Below you'll find the recent presentation at the BattleMesh 8 event that started the worry wheels turning. »youtu.be/LnorCwNyDHo







News Jump Comcast Shuts Off Internet for Subs Who Were Sold Service Illegally; AT&T, Verizon Team To Stop T-Mobile 5G; + more news California Defends Its Net Neutrality Law; AT&T's Traffic Up 20% Despite Data Traffic Actually Being Down; + more news Are The Comcast-Charter X1 Talks Dead In The Water?; AT&T May Offer Phone Plans With Ads For Discounts; + more news Europe's Top Court: Net Neutrality Rules Bar Zero Rating; ViacomCBS To Rebrand CBS All Access As Paramount+; + more news Verizon To Buy Reseller TracFone For $7B; 5G Not The Competitive Threat To Cable Many Thought It Would Be; + more news MS.Wants Records From AT&T On $300M Project; Google Fiber Outages In Austin, Houston, Other Texan Cities; + more news States With The Biggest Decreases In Speed; AT&T Hopes You'll Forget Its Fight Against Accurate Maps; + more news AT&T's CEO Has A Familiar $olution To US Broadband Woes; EarthLink Files Suit Against Charter; + more news 5G Doesn't Live Up To Hype, AT&T's 5G Slower Than Its 4G; Cord-Cutting Now In 37% of Broadband Households; + more news FCC Cited False Broadband Data Despite Warnings; ZTE, Huawei Replacement Cost Is $1.87B, But Only $1B Allocated; + more ---------------------- this week last week most discussed

Most recommended from 50 comments

big_e

join:2011-03-05 6 recommendations big_e Member I can think of 3 reasons why the FCC wants to do this. 1. FBI

2. DHS

3. NSA



Any computing or communications device that doesn't have a backdoor to allow those agencies complete and unfettered covert access is considered a risk to national security.

paradigmfl

join:2005-07-16 5 recommendations paradigmfl Member It's about money Banning custom firmware helps the router makers keep charging you $200+ for a decent router. They don't want you to be able to flash a $40 router and make it full featured once you delete the original "crippleware" that was there before.



Remember the old routers which couldn't handle more than 200 connections yet somehow magically once you flashed them with dd-wrt they could easily handle 1000+ connections?



I wouldn't be surprised to learn that this part of the bill comes from industry incumbents.

ctaranto

join:2011-12-14

MA 2 recommendations ctaranto Member Don't touch my Tomato firmware! The 3rd party firmware Tomato has revolutionized consumer routers into amazing devices. I put Shibby's rendition of Tomato on all my routers (started with WRT54g, to Asus RT-N16, and now Asus RT-AC68U).



I do know that Tomato does have the ability to boost the wifi radio (labeled as Transmit Power, rated in mW). Perhaps this is what the FCC is referring to.