Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1740678

Summary: firewalld should use libnftables JSON interface
Product: Red Hat Enterprise Linux 8 Reporter: Eric Garver <egarver>
Component: firewalldAssignee: Eric Garver <egarver>
Status: CLOSED ERRATA QA Contact: Tomas Dolezal <todoleza>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.2CC: jfriesse, jmaxwell, jpeska, todoleza
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: firewalld-0.8.0-1.el8 Doc Type: Enhancement
Doc Text:
Feature: firewalld now uses libnftables. Reason: Allow for faster and more reliable rule application. Result: Better performance and reliability.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:51:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1740670    
Bug Blocks: 1738635, 1751994    

Description Eric Garver 2019-08-13 13:18:06 UTC
Currently firewalld uses calls to the "nft" binary. This is slow and causes lots of forking. We should use the new libnftables JSON interface. This will allow batching and eliminate forking which will drastically speed up rule application.

Comment 2 Jan Friesse 2019-09-12 16:12:11 UTC
This BZ is very important for corosync daemon to make reload of firewall possible without loosing packets and creating new cluster membership (more info - bug 1663588).

Comment 3 Eric Garver 2019-09-12 20:39:28 UTC
Upstream:

52e2becbf7d5 ("improvement: remove transaction flush for RFC3964_IPv4")
3f7419dcb50a ("chore: remove nft build dependency")
1582c5dd736a ("feat: nftables: convert to libnftables JSON interface")
e519f08d33fd ("chore: travis: no longer run testsuite")
3ea3aa7e1c4a ("chore: nftables: remove unused fill_exists() function")
ff713d793c02 ("improvement: if a transaction fails, dump traceback to debug")
a4fa472540b5 ("chore: fw: don't return anything from set_rules()")
719e239fbff1 ("fix: tests/regression/rhbz1601610: add missing CHECK_IPSET")

Comment 8 errata-xmlrpc 2020-04-28 16:51:23 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:1836