From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Eric Garver <eric@garver.life>
Cc: netfilter-devel@vger.kernel.org, Florian Westphal <fw@strlen.de>
Subject: Re: [PATCH net-next] netfilter: nft_fib: allow from forward/input without iif selector
Date: Mon, 20 May 2024 11:36:35 +0200 [thread overview]
Message-ID: <ZksZo2vYHEmxMZZN@calendula> (raw)
In-Reply-To: <20240517153807.90267-1-eric@garver.life>
BTW, one more comment below.
On Fri, May 17, 2024 at 11:38:06AM -0400, Eric Garver wrote:
> This removes the restriction of needing iif selector in the
> forward/input hooks for fib lookups when requested result is
> oif/oifname.
>
> Removing this restriction allows "loose" lookups from the forward hooks.
>
> Signed-off-by: Eric Garver <eric@garver.life>
> ---
> net/ipv4/netfilter/nft_fib_ipv4.c | 3 +--
> net/ipv6/netfilter/nft_fib_ipv6.c | 3 +--
> net/netfilter/nft_fib.c | 8 +++-----
> 3 files changed, 5 insertions(+), 9 deletions(-)
>
> diff --git a/net/ipv4/netfilter/nft_fib_ipv4.c b/net/ipv4/netfilter/nft_fib_ipv4.c
> index 9eee535c64dd..975a4a809058 100644
> --- a/net/ipv4/netfilter/nft_fib_ipv4.c
> +++ b/net/ipv4/netfilter/nft_fib_ipv4.c
> @@ -116,8 +116,7 @@ void nft_fib4_eval(const struct nft_expr *expr, struct nft_regs *regs,
> fl4.daddr = iph->daddr;
> fl4.saddr = get_saddr(iph->saddr);
> } else {
> - if (nft_hook(pkt) == NF_INET_FORWARD &&
> - priv->flags & NFTA_FIB_F_IIF)
> + if (nft_hook(pkt) == NF_INET_FORWARD)
> fl4.flowi4_iif = nft_out(pkt)->ifindex;
is it intentional to remove for the priv->flags & NFTA_FIB_F_IIF here?
Maybe only the last chunk below is required?
> fl4.daddr = iph->saddr;
> diff --git a/net/ipv6/netfilter/nft_fib_ipv6.c b/net/ipv6/netfilter/nft_fib_ipv6.c
> index 36dc14b34388..f95e39e235d3 100644
> --- a/net/ipv6/netfilter/nft_fib_ipv6.c
> +++ b/net/ipv6/netfilter/nft_fib_ipv6.c
> @@ -30,8 +30,7 @@ static int nft_fib6_flowi_init(struct flowi6 *fl6, const struct nft_fib *priv,
> fl6->daddr = iph->daddr;
> fl6->saddr = iph->saddr;
> } else {
> - if (nft_hook(pkt) == NF_INET_FORWARD &&
> - priv->flags & NFTA_FIB_F_IIF)
> + if (nft_hook(pkt) == NF_INET_FORWARD)
> fl6->flowi6_iif = nft_out(pkt)->ifindex;
>
> fl6->daddr = iph->saddr;
> diff --git a/net/netfilter/nft_fib.c b/net/netfilter/nft_fib.c
> index 37cfe6dd712d..b58f62195ff3 100644
> --- a/net/netfilter/nft_fib.c
> +++ b/net/netfilter/nft_fib.c
> @@ -35,11 +35,9 @@ int nft_fib_validate(const struct nft_ctx *ctx, const struct nft_expr *expr,
> switch (priv->result) {
> case NFT_FIB_RESULT_OIF:
> case NFT_FIB_RESULT_OIFNAME:
> - hooks = (1 << NF_INET_PRE_ROUTING);
> - if (priv->flags & NFTA_FIB_F_IIF) {
> - hooks |= (1 << NF_INET_LOCAL_IN) |
> - (1 << NF_INET_FORWARD);
> - }
> + hooks = (1 << NF_INET_PRE_ROUTING) |
> + (1 << NF_INET_LOCAL_IN) |
> + (1 << NF_INET_FORWARD);
I mean: This chunk alone to remove the hook restriction should be good?
Thanks.
> break;
> case NFT_FIB_RESULT_ADDRTYPE:
> if (priv->flags & NFTA_FIB_F_IIF)
> --
> 2.43.0
>
next prev parent reply other threads:[~2024-05-20 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 15:38 [PATCH net-next] netfilter: nft_fib: allow from forward/input without iif selector Eric Garver
2024-05-17 15:44 ` Eric Garver
2024-05-20 9:31 ` Pablo Neira Ayuso
2024-05-20 9:36 ` Pablo Neira Ayuso [this message]
2024-05-20 13:33 ` Eric Garver
-- strict thread matches above, loose matches on Subject: below --
2024-05-17 15:11 Eric Garver
2024-05-17 15:37 ` Eric Garver
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=ZksZo2vYHEmxMZZN@calendula \
--to=pablo@netfilter.org \
--cc=eric@garver.life \
--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.