From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: Fernando Fernandez Mancera <fmancera@suse.de>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org
Subject: Re: [PATCH nft] meta: introduce meta ibrhwdr support
Date: Mon, 13 Oct 2025 22:39:14 +0200 [thread overview]
Message-ID: <aO1jchhd9t07Igq3@calendula> (raw)
In-Reply-To: <aO1XOREzSUUgROcy@strlen.de>
Hi Florian,
On Mon, Oct 13, 2025 at 09:47:05PM +0200, Florian Westphal wrote:
> Fernando Fernandez Mancera <fmancera@suse.de> wrote:
> > Can be used in bridge prerouting hook to redirect the packet to the
> > receiving physical device for processing.
> >
> > table bridge nat {
> > chain PREROUTING {
> > type filter hook prerouting priority 0; policy accept;
> > ether daddr de:ad:00:00:be:ef meta pkttype set host ether daddr set meta ibrhwdr accept
> > }
> > }
>
> Pablo, does the above ok to you?
> I am not sure about 'ibrhwdr'.
I'd suggest: ibrhwaddr, for consistency with other existing ibr
selectors and anything that relates to address uses the suffix 'addr'.
> Will there be an 'obrhwdr'?
No usecase for this so far.
> Or is it for consistency because its envisioned to be used in
> incoming direction?
Using the input device where this frame came from, which is a bridge
port, fetch the address of the upper bridge device on top of it.
It is a bit unix-like looking acronym, arguably not so intuitive, but
I don't have a better idea.
> Patch LGTM, I would apply this and the libnftnl dependency.
next prev parent reply other threads:[~2025-10-13 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 11:35 [PATCH nft] meta: introduce meta ibrhwdr support Fernando Fernandez Mancera
2025-10-13 19:47 ` Florian Westphal
2025-10-13 20:39 ` Pablo Neira Ayuso [this message]
2025-10-14 7:32 ` Fernando Fernandez Mancera
2025-10-14 11:12 ` Florian Westphal
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=aO1jchhd9t07Igq3@calendula \
--to=pablo@netfilter.org \
--cc=coreteam@netfilter.org \
--cc=fmancera@suse.de \
--cc=fw@strlen.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.