Re: [cobalt-developers] [qube3] content filtering

["Leland J. Steinke" <steinkel-cobalt@xxxxxx>]

Bruce Timberlake wrote:
> 
> Leland J. Steinke wrote:
> 
> > How hard should it be to combine the web caching function of a Qube3
> > with an external content-filtering system such as
> > surfwatch/surfcontrol?  Our customer wants to avoid configuring proxies
> > on every workstation and we figured that it could be done once for all
> > on the qube.
> >
> > If this is going to be an exercise in IPChains, so be it.
> 
> It shouldn't be tough at all, provided there is a Linux version of the
> filtering software you want to run.
> 

Well, then it will be tough.  We have an existing NT box running
surfwatch (to be upgraded to surfcontrol) that we use for content
filtering for our normal dialup customers.  Even if we migrated the
filtering to a Linux box, we'd still want it to be separate from the
Qube in question.

on a cisco, I believe we could do a route-map to redirect the web
traffic to the appropriate location.  very processor intensive.  not
amenable to small errors.  With IPChains, I can redirect to a local
port, but I cannot redirect to a port on a remote machine?  Maybe this
is more an exercise in Squid configuration, rather than IPchains...

Anybody got any bright ideas?


Thanks,
Leland