From: Florian Westphal <fw@strlen.de>
To: Phil Sutter <phil@nwl.cc>,
Pablo Neira Ayuso <pablo@netfilter.org>,
shankerwangmiao@gmail.com, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH iptables v2] extensions: libebt_redirect: prevent translation
Date: Wed, 23 Jul 2025 01:31:53 +0200 [thread overview]
Message-ID: <aIAfaY4aZhAUhuXN@strlen.de> (raw)
In-Reply-To: <aH9M6kWerwHmVvGP@orbyte.nwl.cc>
Phil Sutter <phil@nwl.cc> wrote:
> > > calling 'redirect' verdict will manipulate the IP header as well which
> > > we don't want
> >
> > Can you point me to the code that alters the IP header? I can't find
> > anything.
>
> I guess this is a misunderstanding, but continuing along the lines:
> xt_REDIRECT.ko calls nf_nat_redirect() for incoming packets passing the
> incoming interface's IP address as 'newdst' parameter. I assume
> conntrack then executes, no?
Hmmm, I was referring to ebt_redirect, not xt/nft redirect.
Whats the concern here?
inet redirect should be fully functional, if thats wanted, for skbs
passed to bridge local in via ebt_redirect (or nft bridge family
with mac dest rewritten to a local address + altered packet type).
At least I don't see why it would not work.
next prev parent reply other threads:[~2025-07-22 23:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 8:27 [PATCH iptables v2] extensions: libebt_redirect: prevent translation Miao Wang
2025-07-17 8:27 ` Miao Wang via B4 Relay
2025-07-17 10:05 ` Phil Sutter
2025-07-17 12:01 ` Pablo Neira Ayuso
2025-07-17 12:23 ` Phil Sutter
2025-07-19 15:24 ` Florian Westphal
2025-07-22 8:33 ` Phil Sutter
2025-07-22 23:31 ` Florian Westphal [this message]
2025-07-23 11:03 ` Phil Sutter
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=aIAfaY4aZhAUhuXN@strlen.de \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
--cc=shankerwangmiao@gmail.com \
/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.