From: Florian Westphal <fw@strlen.de>
To: Slavko <linux@slavino.sk>
Cc: netfilter ML <netfilter@vger.kernel.org>
Subject: Re: nftables RP filter and loopback
Date: Tue, 22 Apr 2025 14:53:51 +0200 [thread overview]
Message-ID: <20250422125351.GC2092@breakpoint.cc> (raw)
In-Reply-To: <622E44D0-8F02-4663-ABAD-01497C7D6692@slavino.sk>
Slavko <linux@slavino.sk> wrote:
> + from 6.15 it will work even in input hook and lo as expected
Yes.
> + before 6.15 it doesn't work (properly) outside of prerouting
> hook only with lo traffic (other ifaces works)
Yes. fib works fine but not for loopback traffic.
next prev parent reply other threads:[~2025-04-22 12:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 8:49 nftables RP filter and loopback Slavko
2025-04-22 11:43 ` Florian Westphal
2025-04-22 12:32 ` Slavko
2025-04-22 12:53 ` Florian Westphal [this message]
2025-04-22 13:15 ` Slavko
2025-04-22 14:15 ` Pablo Neira Ayuso
2025-04-23 9:10 ` Florian Westphal
2025-04-23 11:51 ` Pablo Neira Ayuso
2025-04-23 12:06 ` Florian Westphal
2025-04-23 20:56 ` Pablo Neira Ayuso
2025-04-23 20:58 ` Pablo Neira Ayuso
2025-04-26 8:39 ` Slavko
2025-04-26 9:24 ` Florian Westphal
2025-04-26 9:40 ` Slavko
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=20250422125351.GC2092@breakpoint.cc \
--to=fw@strlen.de \
--cc=linux@slavino.sk \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox