After implementing Yaqui's ad-blocking scripts, I started getting ideas for some other things to do with this shiny little router firmware that one might normally use another box for, but which (for my purposes, at least) a WRT54GS might still be more than capable of. My CPU load averages below 0.1 when I'm not hitting the web interface and I maintain above 10MB free RAM, so I think there's a bit of room for experimentation. The first idea was to run a minimal web server to forward Yaqui's adblock requests to (to return a blank.gif file) so as to make the web pages affected look a lot cleaner. The second was to use tinyproxy as an anonymizer, though not necessarily transparently in my case; I was mainly interested in using it to hide the User Agent of my PS3 for certain sites that break themselves for it, as well as for any embedded devices that might have the same issue. I tried making TinyProxy work from the OpenWRT ipkg yesterday, but after unpacking the ipkg, tweaking the configuration files and putting it all on /jffs/, it complained that it needed libresolve to run, as well as some other things that seemed specific to OpenWRT - and as my luck would have it, getting that from OpenWRT apparently isn't quite as easy as untaring an ipkg. I found this page: http://nezzen.net/2007/10/15/running-a-web-server-on-a-home-router/ regarding making httpd run separately from the built-in web interface on Tomato and without authentication. Haven't tried it yet. So, what I'm getting at is this. First, can anyone offer any advice regarding the httpd trick described above, if it won't work with Tomato 1.27 for any reason, if there's a glaring security issue, etc? Second, any advice on making tinyproxy work? Is there a guide to compiling software for Tomato out there somewhere? I've done my share of compiling for platforms I was running on myself, but not much for the embedded space and not without at least some documentation. Alternatively, would I be better off switching to OpenWRT? I rather like the GUI for Tomato, especially the smooth QoS, but I'd rather not have to dedicate a second box to running a couple of very simple daemons if I can avoid it.