From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: Eddi Linder <eddi@guardicore.com>,
netfilter-devel@vger.kernel.org, jengelh@inai.de
Subject: Re: REOUTE target extenstion
Date: Wed, 27 May 2015 14:40:37 +0200 [thread overview]
Message-ID: <20150527124037.GA19766@salvia> (raw)
In-Reply-To: <20150527121130.GC23992@breakpoint.cc>
On Wed, May 27, 2015 at 02:11:30PM +0200, Florian Westphal wrote:
> Eddi Linder <eddi@guardicore.com> wrote:
> > TEE is for gateway redirections, which means the redirected device has
> > to have a configured ip, and to be reachable from the original device.
>
> That makes no sense to me. The to-redirected device always needs to be
> reachable. And iptables is L3 and upwards, so I don't see how 1:1
> copying would fit in here.
>
> > Florian, I didn't find the mirror target in the mainline documentation or code.
>
> I meant the tc action:
>
> tc filter add dev eth0 parent $parent protocol ip [..] action mirred egress redirect dev eth1
>
> > REROUTE redirection is more like the openvswitch output action, copy
> > the packet from one device into another.
>
> Sorry, but my feeling is that this is out of scope for iptables.
Agreed.
There is an incomplete patch to add TEE support to nf_tables bridge
family. You only have to specify the destination device as Eddi needs.
Another alternative is to add this TEE support to ebtables, which is
where this belongs.
next prev parent reply other threads:[~2015-05-27 12:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 10:11 REOUTE target extenstion Eddi Linder
2015-05-27 11:37 ` Jan Engelhardt
2015-05-27 11:37 ` Florian Westphal
2015-05-27 11:56 ` Eddi Linder
2015-05-27 12:11 ` Florian Westphal
2015-05-27 12:40 ` Pablo Neira Ayuso [this message]
2015-05-29 12:02 ` Eddi Linder
2015-05-29 12:50 ` Jan Engelhardt
2015-05-31 11:49 ` Eddi Linder
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=20150527124037.GA19766@salvia \
--to=pablo@netfilter.org \
--cc=eddi@guardicore.com \
--cc=fw@strlen.de \
--cc=jengelh@inai.de \
--cc=netfilter-devel@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 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.