I’ve been interested in custom and open-source router firmware since the early noughties, when Linksys and NetComm began using GPL components and subsequently were required to publish their source code, and did so in an incredibly-difficult-to-compile manner. On and off over the past couple of years I’ve looked at DD-WRT and OpenWRT, two of the more popular open source router firmware distributions, but never had a compelling reason to mess with them. The passage of the Metadata Retention Act into Australia, I think, changes that and makes encapsulating everything I do in a VPN much more compelling. Since I’ll be messing with router settings anyway, why not mess properly?
The answer used to be “because you can”. When Linksys first published the source code for their firmware it took the world by storm.
OK, let me rephrase. It took the Linux-using, free software-loving portion of the software development community by storm. But, you know, that’s still pretty significant.
At the time it was little more than an enforced release because they were using some GPL’d libraries (and my half-hearted attempts to even get it to compile were fruitless). But over time cleverer people and cross compilers put together DD-WRT and OpenWRT custom firmware releases. Over time they developed and diverged, and were joined by a lot of other options.
Currently the three biggies are DD-WRT (feature rich), OpenWRT (package-based, essentially a Linux distro for your router) and Tomato (Pretty and user-friendly). Each of them let you tweak router configuration and do things you can’t do from a typical router configuration interface. So the big reasons to use one are to gain extra control, functions or analytics from your router.
I don’t have a lot of time and (I assume) picking and choosing packages will take a bit of that, so OpenWRT is out.
I want the capacity to play and tweak, and want solid VPN configuration and performance, which makes me lean more toward DD-WRT than Tomato. Decision made.
The obvious choice is the router plugged into your wall right now. The obvious consequence of that, however, is that you’ll be out of Internet during the upgrade. Possibly longer if things don’t go to plan.
In any event, in my case my current router is about four years old, was cheap at the time, struggles to stream things to my Apple TV and, if it started having to tunnel all traffic through a VPN, would probably have a heart attack. All in all a good set of excuses to get a new router.
I spent some time Googling, comparing and reading reviews and ended up with the Netgear R7000 Nighthawk.
Now it’s time to download firmware versions and a copy of the DD-WRT installation instructions just in case things don’t go to plan. Normally this is simply a case of looking up your router in the supported routers database and downloading the initial ROM and, possibly, an additional recommended ROM. It turns out the NightHawk is a special case here, however, and isn’t listed in the database. Hmmmm…
But it’s far from unsupported. Useful documentation is still relatively prevalent, and if you look around there are loads of good resources. But the one you should pay attention to if you’re using a NightHawk (it’s updated every couple of weeks) is this forum post.
- General DD-WRT installation instructions
- General DD-WRT tutorials
- Someone else’s NightHawk installation blog entry
And of course, the ROMS:
- NightHawk Only - http://www.desipro.de/ddwrt-ren/K3-AC-Arm/
- NightHawk Only - http://desipro.de/ddwrt/K3-AC-Arm/
Which ROM to install isn’t so straightforward if you’re using a NightHawk and nobody seems willing to give advice. If you’re not using a NightHawk, just download whatever the supported routers database tells you to. The detailed forum post says the last build with working bridge mode was 26125, but that is very old, and it also lists several problems fixed in February and March 2015. So what the hey, maybe the very latest build is the best idea?
For me that’s 2015-05-19, so down it comes. As does the latest stock firmware from NetGear, just in case it all goes wrong I want to have that handy.
Time to install it.
Connect your computer to your router with an ethernet cable and, if it’s not a brand new router, clear your web browser’s cache.
Log into your router’s management page, find the page to upload a new firmware version, and upload the DD-WRT initial firmware. Continue through any warnings you get and wait for the process to complete in full. Do what’s necessary for a factory reset to clear NVRAM, for the NightHawk this is easy - Just go to its management page (you’ll need to set an initial username and password first), then:
This will result in a reboot and you’ll need to again set an initial username and password. Configure the router as you need to, but here are some tidbits
It seems like setting an upper-upper extension channel makes a considerable difference - I have’t yet had time to trial different combinations of settings, but this is what I’m currently using.
On a Mac, you can get some useful information on your network connection by option-clicking on the wireless icon in the menu bar:
As you can see, the current connection speed is nearly 900MB/s, so I’m not too worried about testing different combinations of settings at the moment.