ASUSWRT vs Tomato

Tried ASUS RT-N10P with stock ASUSWRT and Tomato. ASUSWRT is a fork of Tomato. ASUS put a fancy and heavy GUI to Tomato, and cut off many useful Tomato features. After a week of using ASUSWRT, I finally switched back to good and old Tomato. Below are some grips that make me ditched ASUSWRT.

1. ASUSWRT's Admin GUI only supports single logged-in session. If you closed the admin GUI on one computer, you will not be able to login on another computer unless you log out the GUI session from the first computer.
2. ASUSWRT's QoS does not support classification based on source port. It is critical for remote admin on a router swamped with traffic. On Tomato, you can set TCP 8080 highest to ensure you remote admin session from office to home router is always responsive.
3. ASUSWRT's QoS rules can not be re-ordered for best execution efficiency.
4. When configuring ASUSWRT without WAN port plugged in, the admin GUI is very slow.
5. ASUSWRT only has PPTP VPN server and client. There is no OpenVPN support.
6. ASUSWRT's QoS does not have the useful QoS gragh/pie chart.

There are actually tons of features in Tomato that you may find useful but can not be found in ASUSWRT. Nevertheless, it is a good thing for average home users who just want to set up and go in a few minutes. And QoS in ASUSWRT works well while most of QoS in other home routers fail. For people who wants and enjoy tweaking, Tomato wins hand down.

I eventually flashed Tomato Shibby into my RT-N10P bought for $10 from TigerDirect, and have a big smile on my face.