For the record, i am using squid 3.3.3 and TPROXY working with
Shorewall Firewall 4.5.14 without any problem.
420M 46G TPROXY tcp -- eth5 * 0.0.0.0/0
0.0.0.0/0 tcp dpt:80 TPROXY redirect 10.0.0.99:3129 mark
0x200/0x200
http://www.shorewall.net/Shorewall_Squid_Usage.html#TPROXY
Regards
On Tue, Mar 19, 2013 at 08:49:25PM +0200, Eliezer Croitoru wrote:
Hey Oleg, I want to understand couple things about the situation.
what
is the problem? a memory leak?
1 problem - memory leak;
2 problem - tproxy doesn't work in squid 3.2.
How do you see the memory leak? and where?
I just start squid, start top and wait about a hour when squid grow
from
40MB to 800MB and kernel kills it.
It's hard to say. I was run squid 3.2, with no working tproxy (as i
wrote), but with normal proxy on 3128 tcp port and it eat my memory
too.
So, tproxy is configured, but not used. w
oad of the proxy cache? do you use it for filtering or just plain
cache?
r filtering. on what enviro
kquote>
What do
nvironment? the more details you can give o
io and point with your finger on the problem I will be happy to
assist
us finding the culprit. What linux distro are you using?
Debian 6 and also trie
/pre>
