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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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? Is one or the other more economic with regard to CPU cycles and/or responsiveness?



Been also wondering about potential conflicts between kernel parameters vs. firewall rules, which takes precedence?

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;



Looked into various publications, including [1], but came up short in discovering the hierarchy of /proc parameters vs firewall rules/chains, i.e.

* is the kernel treating both the same or considers one or the other weighing more/higher than the other? * if treated equally does timing in availability of structures cancels out the other, e.g. first available sets the rule or the last one available cancels out the earlier one?

____
[1] https://www.kernel.org/doc/Documentation/filesystems/proc.txt





[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux