From: Florian Westphal <fw@strlen.de>
To: Matthijs Kooijman <matthijs@stdin.nl>,
Stephen Hemminger <stephen@networkplumber.org>,
Bart De Schuymer <bart.de.schuymer@pandora.be>,
bridge@lists.linux-foundation.org,
netfilter-devel@vger.kernel.org
Subject: Re: [Bridge] Unable to DNAT packets back into originating bridge port
Date: Fri, 27 Jun 2014 18:52:13 -0000 [thread overview]
Message-ID: <20140627185207.GA2843@breakpoint.cc> (raw)
In-Reply-To: <20140627174837.GG1353@login.tika.stderr.nl>
Matthijs Kooijman <matthijs@stdin.nl> wrote:
> I recently stumbled upon an issue in my iptables setup. After some
> extensive debugging, I've found that the problem occurs when trying to
> DNAT (+SNAT) a packet that comes in through a bridge, back into the same bridge
> port it originated from.
>
> The code ultimately responsible for this is the should_deliver function
> [1], which prevents packets from being delivered back to their
> originating port (ultimately to prevent bouncing broadcast message, I
> believe).
Sounds like
http://marc.info/?t=136627796900001&r=1&w=2
WARNING: multiple messages have this Message-ID (diff)
From: Florian Westphal <fw@strlen.de>
To: Matthijs Kooijman <matthijs@stdin.nl>,
Stephen Hemminger <stephen@networkplumber.org>,
Bart De Schuymer <bart.de.schuymer@pandora.be>,
bridge@lists.linux-foundation.org,
netfilter-devel@vger.kernel.org
Subject: Re: Unable to DNAT packets back into originating bridge port
Date: Fri, 27 Jun 2014 20:52:07 +0200 [thread overview]
Message-ID: <20140627185207.GA2843@breakpoint.cc> (raw)
In-Reply-To: <20140627174837.GG1353@login.tika.stderr.nl>
Matthijs Kooijman <matthijs@stdin.nl> wrote:
> I recently stumbled upon an issue in my iptables setup. After some
> extensive debugging, I've found that the problem occurs when trying to
> DNAT (+SNAT) a packet that comes in through a bridge, back into the same bridge
> port it originated from.
>
> The code ultimately responsible for this is the should_deliver function
> [1], which prevents packets from being delivered back to their
> originating port (ultimately to prevent bouncing broadcast message, I
> believe).
Sounds like
http://marc.info/?t=136627796900001&r=1&w=2
next prev parent reply other threads:[~2014-06-27 18:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 17:48 Unable to DNAT packets back into originating bridge port Matthijs Kooijman
2014-06-27 18:33 ` [Bridge] " Matthijs Kooijman
2014-06-27 18:52 ` Florian Westphal [this message]
2014-06-27 18:52 ` Florian Westphal
2014-06-27 20:00 ` Matthijs Kooijman
2014-06-27 20:01 ` [Bridge] " Matthijs Kooijman
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=20140627185207.GA2843@breakpoint.cc \
--to=fw@strlen.de \
--cc=bart.de.schuymer@pandora.be \
--cc=bridge@lists.linux-foundation.org \
--cc=matthijs@stdin.nl \
--cc=netfilter-devel@vger.kernel.org \
--cc=stephen@networkplumber.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.