Hacker News Reader

Comment by wycy | Hacker News Reader

What is the best alternative router firmware these days? The last time I looked into this, I believe it was between DD-WRT and Tomato.

View on HN

DD-WRT hasnt had a stable release in 11 years.

Tomato hasn't had a stable release in 9 years.

OPEN-WRT is a fork of DD-WRT. Lede was a fork of OPEN-WRT, but has remerged with OPEN-WRT. OPEN-WRT is the best firmware for home routers/access points in my opinion.

OpenWrt is not a DD-WRT fork.

Well I'll be damned -- It's a fork of WRT54G.

dd-wrt had a better web interface in the early days, and they took copies the OpenWrt kernel in 2005.

It used to be that dd-wrt was less open than openwrt, but worked better. I think now, though, openwrt has surpassed dd-wrt.

https://en.m.wikipedia.org/wiki/DD-WRT

dd-wrt is willing to include closed binaries from router MFGs so they tend to support a larger list of hardware than OpenWRT and on certain models have far better performance. OpenWRT has a massive community supporting it so, in general I'd say they're progressing faster/adding more features.

If you have the luxury of buying new hardware, I would go the OpenWRT route but just make sure you read EVERYTHING on the hardware support page before pulling the trigger. If you're trying to convert an existing router, definitely do research on both, there are advantages to each. Personally if I had a router supported fully by both, I'd go OpenWRT at this point.

Dd-wrt was still a lot more stable every single time onva wrt-1900ac.

I've not had issues on my 1900AC running OpenWRT. The only problem I had was locking myself out when I forgot the credentials....

I wanted to test DD-WRT couple of months ago, but figured out they still use kernel v3.2 for my and couple of another devices (TL&Netgear).

FYI, tomato has a still kicking fork:

https://exotic.se/freshtomato/

> What is the best alternative router firmware these days

I don't know that there is one.

My experience these days when I install a new wifi router is wading through pages and pages of forum posts to try and identify the firmware (or particular build thereof) that will work best on the particular hardware I am configuring that day.

Usually, after a few hours of digging, I sort of "converge" on a particular firmware and a particular release.

Then it's on to experimenting if the thing actually works. If it doesn't, rinse and repeat.

This is very frustrating, and for a number of reasons:

    - From a security perspective, you end up installing a random unvetted piece of binary software on what is basically the gate holding the fort secure.

    - You operate on hearsay (forum posts)

    - There is no guarantee the process will converge.

That's the old way of doing things. And I've been there. Do I want Tomato Shibby.. or will this other weird ROM work better? Hmm, the home page isn't in English on this one. And this other fork was last released March 2011..

No more of that. Today, buy a router OpenWrt supports and just install the official images and get on with your life.

The generic answer:

1. OpenWRT for the most flexibility but you have to edit config files for the more obscure stuff. Tends to take more memory/CPU than others and tends not to run well on older hardware. An entire platform.

2. DD-WRT for the most features available from the web interface. Older versions are suggested for older hardware but that might have security implications.

3. Tomato for the easiest and nicest web configuration interface. Does not support as wide a range of hardware as the others. Might also have issues with older hardware for more obscure features.

I think it’s OpnSense or PFSense but requires hardware that it can run on. Not consumer grade firewalls.

The days of a $50 router in the home having great software seem to be over.

You can run them on an old computer. Used mini-towers and desktop form factor can be had for close to free.

The next major release of pfSense will require hardware encryption support (e.g., AES-NI).

OPNSense is very reliable, but has fewer features though is in active development. Haven't used it in around 18 months or so.

I picked up an HP 4-port 1gbps PCIe card for $40.

However a router is energy sensitive as it runs 24/7. I wouldn't want to run a desktop for this.

Just install a low power CPU. You can get one on eBay delivered for a little more than USPS 1st class shipping. Most of my devices, including my NAS, consume 25-35w, so up to 15w additional consumption, as checked with Kill-A-Watt.

Ever do a tiny load of laundry to get one shirt clean? You've just used something like a year of computer running.

Do you run your air conditioning while your refrigerator exhausts into your kitchen? I call that a kitchen heater. You're heating a cooled space.

I find for whatever reason, tech people all worry about the energy consumed by tiny devices.

There are other power usage concerns beyond cost. For example, if a small room can't have air conditioning you might want only very low power devices to keep from heating it up.

~35 watts isn't actually all that much heat load, and that's what you get from the likes of a business-class Core i5 at the loads routing packets would put on it (i.e. basically idle). Something like Atom or AMD Bobcat is <15 watts.

Another thing to keep in mind if you're worried about power/heat is that 3.5" spinning rust can pull >5 watts per spindle. I've seen 15K drives pull close to 20. But an SSD is close to nothing and so are most 2.5" laptop spindles.

I'll concede that a small closet can get pretty warm from even lower power devices. However, as long as the CPU isn't overheating and the space is clean and dry, it doesn't matter.

Not an expert here, anyway for not too weak x86 hardware (port to ARM is in progress though) I found OpnSense to be a wonderful choice, while for repurposed home routers where the different architecture, memory size and CPU capabilities would make it impossible, I believe the only currently supported one is OpenWRT which I like a lot less, although I concur many of its limitations would probably affect OpnSense too if it was forced to run under the same hardware constraints. I run for several years a PFsense home router, before it was forked to OpnSense, on a PCengines board: https://pcengines.ch/ It worked flawlessly for years, and when a problematic migration from one ISP to a different one forced me out of the Internet for a few months (yup, months!) All I had to do was setting up the WiFi card as WAN and some rules to use it as such, connect a higher gain antenna then find an open spot (there were a lot back then) in my area and bingo: instant connection to the whole house, even much faster than the one I had before. All this perfectly doable with OpenWRT too, but the OpnSense interface at least to me is much much more clear to operate and helps me to understand what I'm doing. Last time I used OpenWRT was to convert one of those micro tp-link "3G" routers so that it connected my LAN only printer to the house WiFi network; in the end all went ok, and it works like charm, though honestly if I had to replicate what I did, I would surely have to read the howtos thoroughly and fail another dozen times again because an extremely simple operation was split into so many others in different pages that I've completely forgotten what I did. OpenWRT is great, potentially even better than OpnSense and other BSD based ones, due to the huge availability of drivers and supported hardware Linux can count on, but it badly needs some good improvements in usability.

Reply on news.ycombinator.com