Hi All,<br><br>Thanks for the reply<br><br>We have used squid2.7stable6 with tproxy4 patch from visolve<br><br>Here is the link for patch <a href="http://www.visolve.com/squid/Squid-2.7-Tproxy-4.patch.gz">http://www.visolve.com/squid/Squid-2.7-Tproxy-4.patch.gz</a><br>
<br>Regards<br>senthil<br><br><div class="gmail_quote">On Wed, May 26, 2010 at 3:07 PM, sameer khan <span dir="ltr"><<a href="mailto:khanzadap@hotmail.com">khanzadap@hotmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
hey,<br>
<br>
what squid version are you using 2.7 or 3.1. if 3.1 then will this workaround will work for 2.7 as well ?<br>
<br>
<br>
thanks and regards<br>
<br>
----------------------------------------<br>
> Date: Wed, 26 May 2010 10:08:22 +0530<br>
> From: <a href="mailto:vivek@visolve.com">vivek@visolve.com</a><br>
> To: <a href="mailto:tproxy@lists.balabit.hu">tproxy@lists.balabit.hu</a><br>
> Subject: [tproxy] Fwd: [squid-users] Squid + Tproxy + Bridge on Kernel 2.6.34 - Workaround<br>
><br>
> FYI -<br>
><br>
> -------- Original Message --------<br>
> Subject: [squid-users] Squid + Tproxy + Bridge on Kernel 2.6.34 -<br>
> Workaround<br>
> Date: Wed, 26 May 2010 09:51:39 +0530<br>
> From: senthilkumaar2021<br>
> To: <a href="mailto:squid-users@squid-cache.org">squid-users@squid-cache.org</a><br>
> CC: <a href="mailto:netfilter@vger.kernel.org">netfilter@vger.kernel.org</a><br>
><br>
> Hi,<br>
><br>
> Squid + Tproxy + Bridge Setup on latest kernel - version 2.6.34<br>
><br>
> I had followed all the steps that had given in the<br>
> <a href="http://wiki.squid-cache.org/Features/Tproxy4" target="_blank">http://wiki.squid-cache.org/Features/Tproxy4</a><br>
><br>
> Kernel - 2.6.34<br>
> iptable - 1.4.8<br>
> ebtable - 2.0.9-1<br>
><br>
> But clients were unable to browse and no errors in cache.log. Error -<br>
> Network Unreachable. The error had returned by browser not squid proxy.<br>
><br>
> Workaround :-<br>
><br>
> After adding the following rules, clients are able to browse.<br>
><br>
> # ip rule add dev fwmark 1 lookup 100<br>
><br>
> example<br>
><br>
> # ip rule add dev eth0 fwmark 1 lookup 100<br>
><br>
> NOTE : Repeat the above for each interface except " lo "<br>
><br>
> Source -<a href="https://lists.balabit.hu/pipermail/tproxy/2010-January/001212.html" target="_blank">https://lists.balabit.hu/pipermail/tproxy/2010-January/001212.html</a><br>
><br>
> Based on the above source this issue had identified on kernel version -<br>
> 2.6.32. But still not yet fixed.<br>
><br>
> I have CC ed this mail to netfilter mailing lists also.<br>
><br>
> Hope this helps<br>
><br>
> Thanks,<br>
> Senthil<br>
><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> tproxy mailing list<br>
> <a href="mailto:tproxy@lists.balabit.hu">tproxy@lists.balabit.hu</a><br>
> <a href="https://lists.balabit.hu/mailman/listinfo/tproxy" target="_blank">https://lists.balabit.hu/mailman/listinfo/tproxy</a><br>
<div class="hm"><br>
_________________________________________________________________<br>
<a href="http://clk.atdmt.com/UKM/go/197222280/direct/01/" target="_blank">http://clk.atdmt.com/UKM/go/197222280/direct/01/</a><br>
Do you have a story that started on Hotmail? Tell us now<br>
_______________________________________________<br>
tproxy mailing list<br>
<a href="mailto:tproxy@lists.balabit.hu">tproxy@lists.balabit.hu</a><br>
<a href="https://lists.balabit.hu/mailman/listinfo/tproxy" target="_blank">https://lists.balabit.hu/mailman/listinfo/tproxy</a><br>
</div></blockquote></div><br>