Gavin McCullagh wrote:
Hi,
there's been a lot of talk about TPROXY being added back into the linux
kernel and squid changing to support it.
Currently, we do transparent proxying by policy routing port 80 traffic to
the proxy server then using DNAT (iptables) on the proxy server.
Could someone point me to something that explains the benefit of TPROXY
over DNAT? We would look to migrate over if there's a substantial benefit.
Thanks in advance,
Gavin
The only documentation I know of that attempts to compare is the readme
by Balabit.
http://www.balabit.com/downloads/files/tproxy/README.txt
The following is based on my knowledge of TPROXYv4, I can't speak for
the older obsolete TPROXYv2.
Not requiring NAT to operate it is not limited in quite the same ways.
It's also much more efficient from an application viewpoint and has the
possibility of being coded to support other protocols such as IPv6 where
NAT is not possible. (Though kernel support still has to be written for
non-IPv4).
The other side is that it is a true source-spoofing mechanism which is
both a pro and con. It's a real invisible proxy. But triangle-of-doom
routing causes greater havoc and much harder to fix.
Overall, I see it as a much better alternative to the NAT methods if
both are available to you and one needs to be used. But is not really
something to normally go out and look for specially.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE6 or 3.0.STABLE15
Current Beta Squid 3.1.0.8 or 3.0.STABLE16-RC1
