Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Ludovico Cavedon <ludovico.cavedon@gmail.com>
To: netfilter@vger.kernel.org
Subject: Re: Need POSTROUTING traversed twice or at least later
Date: Sat, 31 Oct 2009 16:34:32 -0700	[thread overview]
Message-ID: <4AECC988.4090607@gmail.com> (raw)
In-Reply-To: <4AECBC71.3050909@gmail.com>

Ok,
I found an answer here:
http://marc.info/?l=linux-net&m=121250207920447&w=2

Ludovico Cavedon wrote:
> I am not even sure:
> -why does the packet goes thought ip netfilter when is traversing the
> bridge? I would expect it to be forwarded at link level from vif246.0 to
> brveth0. Than I would expect it to come out from eth0 and go thought
> netfilter.
> 
> Is there avoid to avoid the first evaluation of POSTROUTING, or at least
> have it evaluated also after forwarding from veth0 to eth0?

echo 0 > /proc/sys/net/bridge/bridge-nf-call-iptables

fixes my problem.

Still, I am not sure why evaluating nat POSTROUTING is evaluated only
once...

Thanks,
Ludovico

      reply	other threads:[~2009-10-31 23:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-31 22:38 Need POSTROUTING traversed twice or at least later Ludovico Cavedon
2009-10-31 23:34 ` Ludovico Cavedon [this message]

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=4AECC988.4090607@gmail.com \
    --to=ludovico.cavedon@gmail.com \
    --cc=netfilter@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox