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.
DescriptionOliver Paukstadt
2022-02-16 17:43:23 UTC
Description of problem:
$ firewall-cmd --permanent --new-ipset=temp4 --type=hash:ip --option=maxelem=65536 --option=family=inet --option=hashsize=4096 --option=timeout=14400
is not passed to the backend: No timeout parameter available in ruleset.
This makes nft backend unusable if you want timeout sets and you are stuck with iptables.
$ nft list set ip firewalld temp4
table ip firewalld {
set temp4 {
type ipv4_addr
flags interval
}
}
Version-Release number of selected component (if applicable):
Name : firewalld
Version : 0.9.3
Release : 7.el8
Architecture: noarch
How reproducible:
try the commands above.
Additional info:
Maybe related to units, as the native nft command requires "14400s" to add an set and firewalld works on an integer implicit assuming seconds.
Comment 4RHEL Program Management
2023-08-16 07:28:35 UTC
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.
Description of problem: $ firewall-cmd --permanent --new-ipset=temp4 --type=hash:ip --option=maxelem=65536 --option=family=inet --option=hashsize=4096 --option=timeout=14400 is not passed to the backend: No timeout parameter available in ruleset. This makes nft backend unusable if you want timeout sets and you are stuck with iptables. $ nft list set ip firewalld temp4 table ip firewalld { set temp4 { type ipv4_addr flags interval } } Version-Release number of selected component (if applicable): Name : firewalld Version : 0.9.3 Release : 7.el8 Architecture: noarch How reproducible: try the commands above. Additional info: Maybe related to units, as the native nft command requires "14400s" to add an set and firewalld works on an integer implicit assuming seconds.