On Mon, 30 Jul 2007 16:56:22 -0300 Leonardo Rodrigues Magalhães <leolistas@xxxxxxxxxxxxxx> wrote: > I really think doing that (using squid as personal proxy on > localhost) is FAR from being a smart idea. The bandwidth saving with > a single client will be, certainly, very small IF exists at all. And > even if it happens, probably it doesnt worth all the extra I/O and > memory usage. I have a small home LAN, with 3 people using the router PC as a working machine (read: 3 clients) and basically browsing the same sites. Plus a couple of laptops. I don't want or need to buy an aged dedicated PC and use it as a headless router. It makes sense to me to use squid from localhost as a proxy, since my bandwidth is pretty pricey and limited. Anyway, I still believe transparent proxy setup from localhost should be in the docs. Hope someone will find this thread useful. > At least in my understanding, squid is NOT a personal-usage > software. Yes, and iptables is NOT a personal firewall. I agree. But what choice do we have? I did a quick look around and didn't find too many personal proxies for Linux. Polipo is one example (and arguably it handles caching of incomplete downloads etc better than Squid), but Squid is far more flexible, and resources are not an issue in my case. Andrei
