From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf 0/2] netfilter: nft_fib: ignore icmpv6 packets from ::
Date: Wed, 9 Jun 2021 21:08:35 +0200 [thread overview]
Message-ID: <20210609190835.GA4231@salvia> (raw)
In-Reply-To: <20210608114818.23397-1-fw@strlen.de>
On Tue, Jun 08, 2021 at 01:48:16PM +0200, Florian Westphal wrote:
> Quoting nf bugzilla:
> --------
> Using the following for
> reverse path filtering breaks IPv6 duplicate address detection:
>
> table inet ip46_firewall {
> chain ip46_rpfilter {
> type filter hook prerouting priority raw;
> fib saddr . iif oif missing log prefix "RPFILTER: " drop
> }
> }
>
> This is because packets from :: to ff02::1:ff00/104 will be dropped and thus
> other hosts on the network cannot detect that this host already has the same
> address assigned. The problem can be worked around in nft rules by handling
> such packets specially but I guess it should work as is.
>
> In the kernel in ip6t_rpfilter.c the function rpfilter_mt() checks for
> saddrtype == IPV6_ADDR_ANY. nft_fib_ipv6.c doesn't seem to have an equivalent
> check for this special case.
> --------
>
> First patch adds a test case for this, second patch makes icmpv6 from
> any to link-local bypass the fib lookup, just like loopback packets.
Applied, thanks.
prev parent reply other threads:[~2021-06-09 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 11:48 [PATCH nf 0/2] netfilter: nft_fib: ignore icmpv6 packets from :: Florian Westphal
2021-06-08 11:48 ` [PATCH nf 1/2] selftests: netfilter: add fib test case Florian Westphal
2021-06-08 11:48 ` [PATCH nf 2/2] netfilter: ipv6: skip ipv6 packets from any to link-local Florian Westphal
2021-06-09 19:08 ` Pablo Neira Ayuso [this message]
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=20210609190835.GA4231@salvia \
--to=pablo@netfilter.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).