Then its more a question how to setup iptables, the clients and HAVP.
However, why HAV first ?
This has the danger of squid caching infected files. And HAV will scan
cached files over and over again.
Then squid will be an upstream proxy of HAV. IF HAV supports parent proxies,
then squid should
havp supports parent setup, and as far as I have seen, it should be setup
before squid.
Now, I can always switch this around, and move the squid3 setup to 192.168.0.24
and setup
havp on 192.168.0.1 of course.
But 192.168.0.1 is running debian production and Debian does not
support havp on a
So, at least you will need something like
iptables -t nat -A PREROUTING -i eth3 -p tcp --dport 80 -j DNAT --to
192.168.0.24:80
on the squid-box (default gateway).
But then the question arises: Does HAVP support transparent proxying, like
squid does ?
If it does, then
iptables -t nat -A
