Slashdot Mirror


TP-Link Blocks Open Source Router Firmware To Comply With FCC Rules

An anonymous reader points to an official announcement made by TP-Link, which confirms a report from last month that it is blocking open source firmware: The FCC requires all manufacturers to prevent users from having any direct ability to change RF parameters (frequency limits, output power, country codes, etc.) In order to keep our products compliant with these implemented regulations, TP-LINK is distributing devices that feature country-specific firmware. Devices sold in the United States will have firmware and wireless settings that ensure compliance with local laws and regulations related to transmission power. As a result of these necessary changes, users are not able to flash the current generation of open-source, third-party firmware. We are excited to see the creative ways members of the open-source community update the new firmware to meet their needs. However, TP-LINK does not offer any guarantees or technical support for customers attempting to flash any third-party firmware to their devices. Don't lose all your hopes yet. Developer Sebastian Gottschall, who works on DD-WRT Linux-based firmware, believes that TP-Link hasn't blocked third-party firmware. He adds, "Just the firmware header has been a little bit changed and a region code has been added. This has been introduced in September 2015. DD-WRT for instance does still provide compatible images... in fact it's no lock." Furthermore, Cisco insists that FCC's existing or proposed rules doesn't limit or eliminate the ability of a developer to use open source software.

7 of 36 comments (clear)

  1. require markings for region locking by RichMan · · Score: 2

    There needs to be a requirement that all products that are country/region locked have that fact clearly displayed on any product advertising and packaging. The public needs to be aware that something they buy will become unusable if they travel or move with it.

    I am sorry you laptop/phone does not work while you are in mexico/canada/......

  2. So when there's a security hole in an old box by Z00L00K · · Score: 3, Insightful

    So when there's a security hole in an old box - will TP-Link fix that or will they just say "buy a new box"?

    --
    If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    1. Re:So when there's a security hole in an old box by fuzzyf · · Score: 2

      I got myself a TP link earlier that included a backdoor, mentioned earlier on slashdot.
      http://tech.slashdot.org/story...

      So I asked support when they would fix it. The reply I got told me to just make sure nobody got into my LAN and things would be ok.

      Never bying anything TP again. Ever.

  3. Wink Wink by mpoulton · · Score: 4, Insightful

    "As a result of these necessary changes, users are not able to flash the current generation of open-source, third-party firmware. We are excited to see the creative ways members of the open-source community update the new firmware to meet their needs." That's a pretty obvious wink and nod there. "We are required to make it look like we're actually trying to stop you from doing this. We look forward to seeing all the new ways you figure out how to do it anyway."

    --
    I am a geek attorney, but not your geek attorney unless you've already retained me. This is not legal advice.
    1. Re:Wink Wink by snowgirl · · Score: 3, Informative

      Eh... this is more of a “we look forward to F/OSS developers developing ways of ensuring region coding matches the installing firmware.”

      They're not really locking anything, they're just adding a region-locking value that must match before the image is flashed. Honestly, you could just work around this by providing the same image with all the different region-codes.

      But I think they're hoping that the F/OSS community will develop a way of ensuring that specific region-codes get a specific firmware that ensures it complies with the RF transmission regulations of that region.

      --
      WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
  4. Translation... by Frosty+Piss · · Score: 2

    TP-LINK: "We really don't want to have to deal with the FCC on this, so we're going to huff and puff a little for show, and add this little piece of easily bypassable code to cover our asses..."

    --
    If you want news from today, you have to come back tomorrow.
  5. This may sound unpopular, but... by Lobsang · · Score: 2

    Well yes, I gave up OpenWRT and DD-WRT a while ago. It's not that I don't like those projects -- I've used them extensively and respect their authors. The problem is that they're plagued by bugs that never get fixed and compatibility issues with all sorts of devices. For instance, just try to find the "right" version of DD-WRT to download to your wireless router and you'll see what I'm talking about.

    What we need now is an open *hardware* platform, running Linux, with a quality radio and Wireless drivers. I'd go completely crazy for a Linux powered beast like this doing AC1900 or something like that. I'd definitely pay *more* for this platform.

    And screw all the TP-assholes and NET-assholes.