All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Daniel Lucio Quiroz <luis.daniel.lucio@gmail.com>
To: squid-users@squid-cache.org
Cc: senthilkumaar2021 <senthilkumaar2021@gmail.com>,
	netfilter@vger.kernel.org
Subject: Re: [squid-users] Squid + Tproxy + Bridge on Kernel 2.6.34 - Workaround
Date: Tue, 15 Jun 2010 13:37:48 -0500	[thread overview]
Message-ID: <201006151337.48731.luis.daniel.lucio@gmail.com> (raw)
In-Reply-To: <4BFCA1D3.3060505@gmail.com>

Le mardi 25 mai 2010 23:21:39, senthilkumaar2021 a écrit :
> Hi,
> 
> Squid + Tproxy + Bridge Setup on latest kernel - version 2.6.34
> 
> I had followed all the steps that had given in the
> http://wiki.squid-cache.org/Features/Tproxy4
> 
> Kernel - 2.6.34
> iptable - 1.4.8
> ebtable - 2.0.9-1
> 
> But clients were unable to browse and no errors in cache.log. Error -
> Network Unreachable. The error had returned by browser not squid proxy.
> 
> Workaround :-
> 
> After adding the following rules, clients are able to browse.
> 
> # ip rule add dev <device name> fwmark 1 lookup 100
> 
> example
> 
> # ip rule add dev eth0 fwmark 1 lookup 100
> 
> NOTE : Repeat the above for each interface except " lo "
> 
> Source - https://lists.balabit.hu/pipermail/tproxy/2010-January/001212.html
> 
> Based on the above source this issue had identified on kernel version -
> 2.6.32. But still not yet fixed.
> 
> I have CC ed this mail to netfilter mailing lists also.
> 
> Hope this helps
> 
> Thanks,
> Senthil

I was about to  ask
if this is fixed in 2.6.33+

or shall i stay in 2.6.31.x

  reply	other threads:[~2010-06-15 18:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26  4:21 Squid + Tproxy + Bridge on Kernel 2.6.34 - Workaround senthilkumaar2021
2010-06-15 18:37 ` Luis Daniel Lucio Quiroz [this message]
2010-06-16  3:44   ` Amos Jeffries

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201006151337.48731.luis.daniel.lucio@gmail.com \
    --to=luis.daniel.lucio@gmail.com \
    --cc=netfilter@vger.kernel.org \
    --cc=senthilkumaar2021@gmail.com \
    --cc=squid-users@squid-cache.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.