I have had this problem. I have found that part of the problem is that when the iptables rules are entered at the CLI, they are not added in the correct order required for functioning. I have also seen cases where the client web surfing keeps timing out, and either after timeout or after the client clicks the stop button, the access shows up in the access.log. I find that I have add the iptables rules via the cli, do an "service iptables save", then "vim /etc/sysconfig/iptables" and rearrange the rules. -----Original Message----- From: Benjamin [mailto:benjo11111@xxxxxxxxx] Sent: Thursday, August 18, 2011 2:11 PM To: squid-users@xxxxxxxxxxxxxxx Subject: Re: Re: squid tproxy problem On 08/18/2011 08:19 PM, Amos Jeffries wrote: > 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 Hi Amos, i tried with kernel 2.6.38.8.But i face same issue.When i see packets in iptables tproxy rule , i can not see any requests into access.log also customers are not able to browse sites. and then when i swap interface in ebtables rules , from customer side browsing is working but no packets in tproxy rule and no requests in access.log. I don't find where is the mistake? Regards, Benjamin
