I have one CentOS v6 box running the CentOS v6 supplied 2.6.32-71.29.1.el6 kernel, and iptables-1.4.7-3.el6. I am using a recompiled squid-3 rpm that I popped 3.1.14 into and the combination seems be working fine. I am also testing a CentOS v6 install with a the kernel source rpm from RHEL 6 (kernel-2.6.32-131.6.1.el6), iptables source rpm from RHEL6 (iptables-1.4.7-4), and the squid 3.1.14 rpm I made. I am testing this because there was a TPROXY fixes made in an upstream kernel release that RedHat back-patched. The only issue I have run into thus far is a higher than normal occurrence of TCP_MISS/502 errors in squid. I am not sure if the error is in squid/tproxy/kernel or on the network, but I suspect it is on my network. Nick -----Original Message----- From: Amos Jeffries [mailto:squid3@xxxxxxxxxxxxx] Sent: Thursday, August 18, 2011 9:49 AM To: squid-users@xxxxxxxxxxxxxxx Subject: Re: Re: squid tproxy problem On 19/08/11 01:43, Benjamin wrote: > Hi Amos, > > Thanks for your kind response.I am going to try with latest kernel > 3.0.3 and update u with final status. > > kernel 3.0.3 is ok for tproxy with squid verion 3.1.10 ? > I have no information about it. But I expect so. Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.14 Beta testers wanted for 3.2.0.10
