Ask HN: Tomato or DD-WRT for my router?
I just got a linksys WRT54G V1 wireless router and want to hack the firmware. From my initial research it looks like the two main options are DD-WRT and Tomato. Has anyone here installed either of them and have an idea of which one is better?
Just curious to see what the people here think of those firmware options.
24 comments
[ 4.5 ms ] story [ 68.4 ms ] threadI tend to end up using my wireless gear in dumb WAP mode. This is usually precipitated by wanting full specific control of my firewall/NAT configuration, full control of DHCP and my public IP attached to something with storage. That said, the interface and feature set of DD is nice enough that I'll probably give it a shot next time I flatten my home network, and DD is probably powerful enough that it will stick for a while.
* tunneling: I work mobile and tunnel everything through ssh and/or openvpn using my primary home router.
* signal boost: I can't get reception everywhere I need to without it
* dynamic dns updating: it keeps my dyndns stuff updated automatically
* Wireless bridge: for example, the xbox wireless adapter is $100, but I just took an wrt54g router (about $50) set it up as a bridge and use that. Similar situation for older devices in the kitchen that can't use the wireless on their own.
My router is also a little buggy (really need to buy a new one) and Tomato runs with fewer dropped connections than DD-WRT. I'm sure that has much less to do with the firmware and more to do with bad hardware.
There are lots of options that look as though they would be cool, but I mostly use it as a plain ol' WAP.
I will warn you, and I'm not sure if this issue exists for other *WRT firmwares, but PPTP VPN and OSX is not ideal on DD-WRT: http://www.dd-wrt.com/wiki/index.php/PPTP_Server_Configurati...
OpenVPN is the way to go, but not built in like PPTP is, well, everywhere ...
I ran DD-WRT on a WRT54GL for a few months, and during this time, I kept experiencing intermittent connection problems. I spent hours and hours poring over packet sniffer logs, and finally discovered that the router was the problem.
So I tried switching to Tomato, and it worked perfectly.
(That was 2007, and as far as I know, the bug is still there)
Sorry if my comment came across as saying that DD-WRT is just unreliable..
Have been using it for a couple of years, even running a startup's infrastructure behind it. No problems, whatsoever.
Last time I checked, DD-WRT was just a set of packages on top of OpenWRT, so going with straight OpenWRT lets you add only the functionality you need and customize everything to your heart's content. I would choose that route over DD-WRT. However, I did run into some reliability issues, (wireless connections would drop spontaneously every few weeks) which show up in DD-WRT as well. In OpenWRT, many basic settings (all settings unless you install a web interface) are only accessible via config files. That can get tiring.
Tomato is rock-solid and dead-easy to configure, but startlingly light on functionality compared to *WRT.
If you have the time, try them both!
Go with tomato, its bandwidth monitoring options are awexome
http://www.society9.com/an-easy-guide-to-installing-tomato-o...