Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 19 Nov 2007 18:32:53 +0300
From:      Andrew Pantyukhin <infofarmer@FreeBSD.org>
To:        Steve Bertrand <iaccounts@ibctech.ca>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: FreeBSD router and WCCP
Message-ID:  <20071119153252.GF57722@amilo.cenkes.org>
In-Reply-To: <4741A773.8010101@ibctech.ca>
References:  <473DD804.1020502@ibctech.ca> <20071118151716.GA57722@amilo.cenkes.org> <4741968A.3010009@ibctech.ca> <20071119145205.GE57722@amilo.cenkes.org> <4741A773.8010101@ibctech.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 19, 2007 at 10:10:43AM -0500, Steve Bertrand wrote:
> 
> > ipfw forwarding is a very easy way to redirect traffic without
> > changing it. PF has similar functionality. It all depends on what
> > the appliance supports. If wccp is the only way it can eat
> > packets, try playing with gre(4). But maybe it'll consume just
> > plain packets with "wrong" IP destinations arriving on its MAC
> > address, just the way squid on FreeBSD does.
> > 
> > BTW, if the appliance supports ICAP, you'll be much better off
> > running squid on a FreeBSD box and filtering content through
> > ICAP.
> 
> The appliance does indeed have ICAP capabilities, but I have never
> dabbled with it before.
> 
> I am familiar with IPFW, but I'd like to know all options in order to
> choose the best one.
> 
> I would very much prefer to do this in a way without having to have
> Squid running on the box, but will if I have to.

If filtering is all you want, you don't have to set up squid as a
caching proxy. I.e. it won't need much RAM and disk space. I have
yet to set up ICAP (with c-icap) in our workshop, but from
discussions on squid mailing lists it seems ICAP is in a pretty
usable state, both in squid 2.x and 3.x.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071119153252.GF57722>