Welcome to WebmasterWorld Guest from 18.104.22.168
Forum Moderators: bakedjake
I keep wondering about setting it up as a proxy cache running Squid. I've never worked with it before. What kind of time frame would it take for me to setup? Is it even worth the hassle? I'm on 512 dsl, but the modern browsers really suck at caching.
Think it is something I would find useful?
I don't particularly use it for its caching functions, more as an access controller, so I don't know how much of an improvement it is over browser caching, but from the amount of tweakables in the config file I suspect it could be pretty effective.
Have you considered using ipchains to turn it into a firewall also?
My linux server was port scanned and attacked about once an hour. That was on dialup, on ADSL I think that number would be (finger in air) sixfold.
I never dial up using windows anymore -- too dangerous ;)
$ rpm -U squid-*.rpm
$ rpm -U bind-*.rpm
$ rpm -U caching-nameserver-*.rpm
Well, not exactly, but you get the point :) Squid is pretty good caching system, and I use it with Fredrik's Sleezeball ([boost.linux.kz ]) to filter the wanted ads. Sleezeball is not a second level proxy like Junkbuster, but it is a URL rewriter plugin for Squid, which rewrite all the banner ads to a static local image.
Setting up a local cache DNS server is easier with RPM-based system since it includes all the configuration file for you. Just install the caching-nameserver and then change your /etc/resolv.conf to
It is definitely much better than the browser based caching, and you get much more options to tune with. Moreover, since it serves the whole intranet, not only your browser can benefit from cached data, so can all other users from the same network.