Bug 2055330

Summary: nft-backend unusable with ipset and timeout
Product: Red Hat Enterprise Linux 8 Reporter: Oliver Paukstadt <pstadt>
Component: firewalldAssignee: Thomas Haller <thaller>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.5CC: egarver, thaller, todoleza
Target Milestone: rcKeywords: TestCaseProvided, Triaged, Upstream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
If this bug requires documentation, please select an appropriate Doc Type value.
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-16 07:28:35 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:

Description Oliver 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 2 Thomas Haller 2023-08-04 14:12:57 UTC
fixed upstream by https://github.com/firewalld/firewalld/pull/1167

Comment 4 RHEL 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.