Description of problem:
NFT created by firewalld do not create counters. They were implicitly present for iptables rules and were helpful with observing or debugging packets going through the installed ruleset.
This request is to add a tunable into firewalld which would implicitly add the counter statement into nft rules.
Version-Release number of selected component (if applicable):
always, nft ruleset used
rules don't log traffic anywhere, not even number of how many times a rule passed a packet through
a global tunable to enable counters for all rules.
FWIW, it's very simple to trace with nftables which may be a better debugging mechanism than counters.
# nft add table inet trace_firewalld
# nft add rule inet trace_firewalld INPUT nftrace set 1
# nft monitor |grep firewalld |grep -i "\(drop\|reject\)"
trace id 5e9e28de inet firewalld filter_INPUT rule reject with icmpx type admin-prohibited (verdict drop)
I've described challenges with use of nftrace in a RFE for nft-monitor in bug 1782526.
tl;dr; the output is really verbose and uncategorised. it uses just a trace id without possibility to further narrow the output when there are e.g. multiple trace enabling rules. that is a problem on bigger-than-low network traffic passing systems.
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.