The important point here is that vendors aren't locking down their firmware because they're control freaks that hate when customers install modified firmware, it's also a big security hole. If you can replace your firmware with a modified copy, so can anyone else who manages to gain access to your device. There's other angles too of course, such as vendors who offer unique hardware may want to require their customers to always be using that business's products, as that's how they make money, but when we're talking about generic equipment like routers, the most important reason is security.
It isn't.
If someone has physical access to your device, you have lost. The end. They could just replace the entire device with one with an identical case but different internals.
But if you successfully prevent attackers from gaining physical access to your device then there is no security cost in granting anyone with physical access full control over the firmware.
And for devices you know will be placed in unsecured areas where you would still like some security theater (or to inhibit meddling by unsophisticated malcontents), there is nothing wrong with allowing the owner to lock the firmware using the owner's key or password.
I realize the security issues, I'm not worried about them. As somebody who wants to learn about embedded Linux development, and who owns several other OpenWRT compatible devices 'locking' the firmware is not something I am interested in.
This argument breaks down when you're not talking about the manufacturer -- at the time the ISP made that modification, they bought it. They owned it. Should they not be permitted to do what they like? Should you not be permitted to write your own firmware which requires headers?
Maybe it's just me, but this seems like an easy thing to get over by buying some different hardware. Instead of stressing out about this particular WNDR3800, focus your angst on the general case, which is the FCC's attempt to make it illegal to upload custom firmware to any router.
This is sophistry. It's not a question of "can" in the sense of "be able (because of your skills) to", but of "the vendor actively prevents it".
And the vendor is surely not preventing you actively from turning your device into a surfboard, a dishwasher, or a birdcage. But he is actively preventing you from turning it into a customized router.
Don't try to make a "freedom" argument here. Vote with your Value and buy an unlocked piece of harware.
See, I bought this WNDR3800 off Ebay, because I wanted to put OpenWRT on it. Its compatible. But I made the mistake of buying a used router that was managed by a ISP. They built their own firmware and purposefully made the firmware updater require specific headers in the firmware package. Now I can't update this device to OpenWRT, without some very specific hacking and compiling my own version of OpenWRT.
Who owns this hardware? I bought it. I paid for it. Its in my house. But apparently this ISP is truly the owner and I can't do anything that I wish with this device.
The firmware is based on Linux, the ISP of course hasn't released their source. The only way I know about the header bit is because somebody else figured this out years ago and there is a single message on a random web forum detail it.
Presumably, the "openness" of the original device running Linux is what allowed them to build their own custom firmware in the first place.