RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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):
firewalld-0.7.0-3.el8

How reproducible:
always, nft ruleset used

Actual results:
rules don't log traffic anywhere, not even number of how many times a rule passed a packet through

Expected results:
a global tunable to enable counters for all rules.

Additional info:

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.