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.
DescriptionDanila Vershinin
2017-10-26 17:12:30 UTC
firewalld.noarch 0.4.4.4-6.el7
Creating an ipset first with:
/usr/bin/firewall-cmd --permanent --new-ipset=countryblock --type=hash:net --option=maxelem=1000000 --option=family=inet --option=hashsize=4096
(note the timeout)
Then later adding entries to the IPset with:
firewall-cmd --permanent --ipset=countryblock --add-entries-from-file=/some/file
Actual results:
Outputs "Error: IPSET_WITH_TIMEOUT"
Expected results:
firewall-cmd should not issue Error when adding entries to ipset which has timeout defined.
Additional information:
Using raw ipset command to add entries for the same works fine:
while read p; do /usr/sbin/ipset -exist add countryblock $p timeout 691200; done < /some/file
(In reply to Danila Vershinin from comment #0)
> firewalld.noarch 0.4.4.4-6.el7
>
>
> Creating an ipset first with:
>
> /usr/bin/firewall-cmd --permanent --new-ipset=countryblock --type=hash:net
> --option=maxelem=1000000 --option=family=inet --option=hashsize=4096
>
> (note the timeout)
>
> Then later adding entries to the IPset with:
>
> firewall-cmd --permanent --ipset=countryblock
> --add-entries-from-file=/some/file
firewalld disallows adding permanent entries to an ipset if the ipset has a timeout. Entries cannot be permanent if they timeout.
It should work if you don't specify --permanent. Can you verify?
It fails with or without --permanent switch:
firewall-cmd --permanent --ipset=countryblock --add-entries-from-file=/some/file
Error: IPSET_WITH_TIMEOUT
firewall-cmd --ipset=countryblock --add-entries-from-file=/some/file
Error: IPSET_WITH_TIMEOUT: countryblock
P.S. in my initial message, the command is/has to be:
/usr/bin/firewall-cmd --permanent --new-ipset=countryblock --type=hash:net --option=maxelem=1000000 --option=family=inet --option=hashsize=4096 --option=timeout=691200 (made a mistake when copy pasting here)
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/RHBA-2018:3120