Re: [nftables] economics of reverse path filtering - FIB expression vs. kernel parameter

[Florian Westphal <fw@strlen.de>]

ѽ҉ᶬḳ℠ <vtol@gmx.net> wrote:
> On 12/02/2020 11:03, ѽ҉ᶬḳ℠ wrote:
> > On 09/02/2020 12:51, ѽ҉ᶬḳ℠ wrote:
> > > Presumably NFT rule
> > > 
> > > * filter prerouting fib saddr . iif oif missing drop
> > > 
> > > and kernel parameter
> > > 
> > > net.ipv4.conf.<interface>.rp_filter = 2
> > > 
> > > achieving the same goal.
> > > 
> > > Which one comes into effect first, if there is difference assuming
> > > that both are being processed through netfilter?

prerouting hook comes before routing decision in network stack, so,
if you drop a packet there it will never make it to the routing
decision.

> > Been also wondering about potential conflicts between kernel parameters
> > Another example - here purposely creating a conflict:
> > 
> > * net.ipv6.conf.<interface>.accept_redirects = 0
> > 
> > vs.
> > 
> > * ip6 saddr fe80::/10 ip6 hoplimit 255 daddr FF02::1 icmpv6 type 137
> > accept;

Accepting packet means that processing continues, it
doesn't have any other effect.

So it doesn't matter if you accept redirect packets in nftables or if you
do not have nftables rules at all.