On Tue, 2004-06-08 at 11:17, Ed K. wrote: > On Tue, 8 Jun 2004, Rodolfo J. Paiz wrote: > > At 10:31 6/8/2004, Chris Kloiber wrote: > >> IIRC, privoxy has a web front-end of it's own to configure it. Squid > >> does not, but you can enable basic squid functionality for your local > >> network by adding 2 lines to the /etc/squid/squid.conf, so it's not hard > >> at all. > > > > And those two lines are... <drum roll please>? > > > > I'm going to get around to installing/configuring squid in a few days and > > I'll do my own reading of the docs then, but I'm curious as to how that > > message would end. <smile> > > > > Cheers, > > Rodolfo J. Paiz > > how about these: > > 1) acl localnet src 10.0.0.0/255.255.0.0 > 2) http_access allow localnet > > of course the '10.0.0.0/255.255.0.0' would be your own network/netmask. > and make sure these lines are before the line: > http_access deny all Well, if you're like me, then perhaps those 2 lines are _not_ needed at all. eg: 1. If you plan only on using it on the _same_ machine you're running it on. (localhost access only) That way, nothing needs to be configured. and though it's an open proxy, so to speak, your firewall rules would deny anyone not from localhost to access it. 2. I use squid in connection with (actually, this is 1 main reason) squid_redirect (after reading it up on www.linuxjournal.com or some other place, I forget) What this does, isit effectively acts as an ad blocker. So, I'm quite happy with it. ps : I've always liked the name squid and it's connection with being a proxy. Connotes the idea that the tentacles from the squid is gonna make thing runs/fetch faster.
