I think the only option I truly appreciate from Tomato is the ease of nvram deletion. I don't really like the interface(other than the snappyness. The good thing it has going for it is the snappiness of the interface, but I wish there was a more professional looking interface for it(I really, REALLY like dd-wrt's interfaces.))
I like how this firmware is light though, unlike dd-wrt. This light feeling is what dd-wrt should have. Currently I am using Victek's firmware on my wrt54gl1.1, didn't bother changing the 10240 connection limit either. The real reason I changed (to tomato) was because dd-wrt v24sp1's QoS managed to do something undesirable. Speedtest.net speed test tells me I have an average of 1320/420 kbit/s down/up.
DD-WRT's QoS made it 1/3rd to 1/5th that(down). Didn't affect the upstream though. Surfing was pretty much impossible on it, and so was everything else.I downgraded to v24(non sp1) Same thing.
Changed to tomato+victek 1.21 and I can say everything works smoothly now.
One thing I hate about it though, is that the QoS is too complicated. It doesn't seem like it tracks downstream/affects downstream either.
I seem to have unclassified QoS connections on the graph, but I cannot tell if it is due to the QoS daemon restarting(resulting in all connections becoming unclassified and thus will take time to propagate into a classified state). What irks me though is that my data isn't classified under class A(which is what I set for bT and whatnot.) Overall it's a great firmware, with more potential than dd-wrt. I just wish that some things were implemented more like dd-wrt though. For example disable wireless upon router reboot.(and use the SES button to start it up.)
The sad thing is that I don't really want to run much scripts on this thing(since it's a bother and I know nuts about scripting) and I only want some things (like QoS) to work flawlessly(which to my surprise is working just fine, but I believe I can fine tune it further.)
So far the experience has been nothing short of wonderful though. Browsing is fine(but for some reason(I believe it's my firefox) sometimes pages don't load properly. Loads fine in Opera though.) even with torrents, online radio, chatting going on in the background.
Overall this was a great experience(better than my tomato 1.19 experience, which was horrible and the reason I went back to dd-wrt) but I wish the QoS was more encompassing(for uploads and downloads) and I wish there was a comprehensive guide(other than "I do this for my settings" because not everyone's setup is the same, I might want to do something they did not outline). And all that I've seen is some threads that are all "I do this for my settings", though I may have missed some things. ( I really liked the rhester thread though, his was very comprehensive and covered many things that isn't usually discussed.)
For example I am using vpn for torrents, and I set my torrents to use class A.
I see nothing in class A, so I set vpn to use class A too( via dst port 1080).
Am I doing it wrong? I don't know, but I still see nothing in class A most of the time(unless bittorrent's udp uses my default port.)
Anyone able to shed some light? I'm really starting to like this, just wish it ran a little differently(interface, some features, etc) and that I'm able to fine-tune my experience further via QoS.
Also anyone able to shed some light on the hardware firewall capabilities of this router?
Define how you link your VPN with your torrent. Is it through a proxy sever , or does it tunnel through directly ?