From: Dominique Martinet <asmadeus@codewreck.org>
To: Andreas Jaggi <andreas.jaggi@waterwave.ch>
Cc: Netfilter Development Mailing list <netfilter-devel@vger.kernel.org>
Subject: Re: ipv6 rpfilter and.. fw mark? problems with wireguard
Date: Fri, 10 Apr 2020 11:14:05 +0200 [thread overview]
Message-ID: <20200410091405.GA5893@nautica> (raw)
In-Reply-To: <CA65DC1B-209F-4C64-9497-38B98406DCFF@waterwave.ch>
Thanks for the prompt reply!
(I just noticed the netfilter@ list, sorry for having asked the question
here instead)
Andreas Jaggi wrote on Fri, Apr 10, 2020:
> > table inet test {
> > chain raw_PREROUTING {
> > type filter hook prerouting priority raw; policy accept;
> > meta nfproto ipv6 fib saddr . iif oif missing log prefix "rpfilter_DROP: " drop
> > }
> > }
> >
> > or
> >
> > ip6tables -t raw -A PREROUTING -m rpfilter --invert -j LOG --log-prefix "rpfilter_DROP: "
> > ip6tables -t raw -A PREROUTING -m rpfilter --invert -j DROP
>
> This does not consider the fwmark for the reverse-routing lookup.
> Using the --validmark option for the rpfilter match should get you the correct result.
>
> And for nft the already suggested:
> meta nfproto ipv6 fib saddr . iif . mark oif missing log prefix "rpfilter_DROP: " drop
Ok.
> I suspect the main problem is the rpfilter check happening in the raw
> table, but the fwmark only being written in the mangle table.
> Thus the rpfilter lookup happens without the correct fwmark and fails
> to return the correct result.
>
> I would move the rpfilter check into the mangle table and place it
> after the fwmark is written.
Ok, firewalld rules are in a different table but they set priorities to
mangle + 10 so I tested something similar and it does work:
table inet test {
chain premangle {
type filter hook prerouting priority mangle + 10; policy accept;
meta nfproto ipv6 fib saddr . mark . iif oif missing log prefix "rpfilter_DROP: " drop
}
}
(I also confirmed moving the iptables, unsurprisingly it works and does
require the --validmark switch suggested)
I also found that adding --loose to the ip6tables rule also works, I've
had a look at the man page[1] and can't say I understand how to make an
equivalent 'loose' rule as nft, but I'll keep trying a while longer.
(I'm asking because the ipv4 default seems to be loose on my setup, so
I'm surprised ipv6 would be different; not decided on what to actually
use)
[1] https://www.netfilter.org/projects/nftables/manpage.html#lbBR
I'll get back to the firewalld developer to discuss what would be
the preferred solution, thanks again for the help.
Cheers,
--
Dominique
prev parent reply other threads:[~2020-04-10 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 20:38 ipv6 rpfilter and.. fw mark? problems with wireguard Dominique Martinet
2020-04-10 8:38 ` Andreas Jaggi
2020-04-10 9:14 ` Dominique Martinet [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=20200410091405.GA5893@nautica \
--to=asmadeus@codewreck.org \
--cc=andreas.jaggi@waterwave.ch \
--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