I've been running tomato from the start on my buffalo whr-g54s. It ran fine for about a month or two, and then dnsmasq started crapping out, and nvram wouldn't commit. Simply resetting everything and reconfiguring brought back nvram functionality. However, dnsmasq is still an issue. I upgraded to the latest tomato, which has a newer dnsmasq, but the problem is still there. And it's more so of a problem now since I am now dealing with about 10 computers on the network instead of 6. And with more people now, it's moreso required to be failsafe. I saw that a lot of people are also having this dnsmasq issue. As a temporary solution, I've set my own computers to run off tomato's dns, but have dhcp set to directly pass the isp's dns as well as 220.127.116.11. This works well for everyone, except if I don't catch on and restart dnsmasq in time, or else when it's time for them to renew dhcp, they croak. I'm trying to narrow down any possible problems, and currently have qos disabled. If it still doesn't improve, I suppose bandwidth monitoring / logging has to go (both at defaults right now).