Love Tomato and have used it forever. Really sorry that Toastman and Shibby have been busy and not able to update at all. The Kille builds look great but they are only for ARM devices. Honestly wish could help keep development going and contribute myself but have no formal knowledge about computers, nothing to do with computers in real life, and cannot program in any language. With the DNSMasq issue decided to switch an access point to a firmware that had DNSMasq updated to 2.78 because the more that read into the DNSMasq issue the more serious that think it is (just sending certain DNS queries with DNSMasq can lead to remote code execution). Remember seeing @koitsu saying a while back how DNSMasq spews way too much local query information to any DNS servers it is using also. It hurt but decided to give another firmware a try to mitigate the DNSMasq issue (was using the access point itself as a DNS server for most machines on network) so it really made sense to get DNSMasq to 2.78 on this access point. Went with Merlin-wrt and hated the interface (and really made want Tomato back) and have a few observations. First WiFi range with the access point with MErlin-wrt is significantly better than with Tomato (probably because of the hardware acceleration or drivers utilized by the official Asus firmware/ Merlin-wrt). Second again the interface used by official firmware and Merlin-wrt is awful. Lastly and most interesting. Say that have a connection where upstream bandwidth is very low and connection maxes out upstream bandwidth. With the Merlin-wrt devices cannot actually connect the WiFi access point when the upstream connection is saturated even though the Merlin-wrt device is only an access point and the traffic isn't even passing through the Merlin-wrt device. Never had any issue like this with Tomato. As soon as the upstream is no longer saturated can reconnect. Can replicate this issue at will which is very interesting. Rarely saturate upstream except for large uploads though so more of an observation that an issue. Merlin-wrt has SSH and some options of Tomato but did not offer nearly everything that Tomato does and yet again the interface is awful. If Tomato MIPS builds can ever get the DNSMasq 2.78 update would love to update all Tomato devices that have. Used to enjoy (honestly it was kind of fun with Tomato) logging into a Tomato router to change something. With the Merlin-wrt interface it is as awful as logging into a router should be. The other thing that would be great is if Merlin took his firmware (utilizing proprietary drivers and hardware acceleration) and gave it a Tomato GUI. Hope this helps anyone struggling with deciding to keep a Tomato device or not with the DNSMasq vulnerability with what can be expected.