We are a small WISP startup about to go online in a few weeks. We will be providing our customers with a wireless router, probably a mass-market model that that is available refurbished for low cost. (We've tentatively chosen the Linksys WRT-160n.) We want to use custom firmware both for security, so we can lock the routers down so people can't use the master reset switch, and for enhanced QoS. We will be reselling VOIP and we want people to have clear phone calls so QoS is important. We've tested both Tomato and DD-WRT and are having a little trouble deciding. The main criteria are QoS performance and future viability of the platform. We don't want to have to change firmware a few years down the road when we decide to change routers. We have the following concerns about Tomato. 1. Toastman's recent builds with named classes and predefined rules are very cool and a good way to get started learning how to configure and use QoS, but they are perhaps overkill for us and we could get by with a simpler implementation. Our QoS requirements are not as rigorous as his, because each of our customers will have a minimum of 4Mb bandwidth. Also, we will not be able to do continuous tweaking. We want to find some settings that we can configure and forget about once the router's in the customer's house. 2. The Tomato community is very much smaller than DD-WRT's and as far as I know is not backed by a commercial company. How can we rely on having updated firmware available in the future? 3. It is alleged that Tomato is based on "buggy original Linksys firmware" based on this FAQ entry: http://www.polarcloud.com/tomatofaq#is_tomato_based_on_linksys_sou Have original linksys bugs been fixed in current tomatoUSB builds? (And isn't dd-wrt based on the same original firmware?) 4. Milkfish? I see no VOIP versions in the tomatoUSB builds. For most of our customers we won't need this but we will have a few business customers who will need it or something similar. 5. Disabling the reset button. Apparently Tomato does not support this. We don't want customers monkeying with the router settings. 6. More hassle to flash. According to the instructions I found for the WRT-160N you have to first flash dd-wrt and then upgrade to tomato. Why can't Tomato be installed directly over the factory firmware? This extra step will be significant when deploying dozens of routers. Thanks for any clarifications you can offer.