Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1775175
Summary: | fail2ban-firewalld should define banaction_allports | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Chris Adams <linux> |
Component: | fail2ban | Assignee: | Orion Poplawski <orion> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 31 | CC: | anon.amish, axel.thimm, orion, vonsch |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | fail2ban-0.10.4-8.fc31 fail2ban-0.10.4-8.fc30 fail2ban-0.10.4-1.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-12-02 01:13:08 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
Chris Adams
2019-11-21 14:17:57 UTC
Thanks. Have you tested both of these to see that they work? Yes, I've got that on a Fedora 29 (which obviously needs an OS upgrade) system right now, and will be adding to a CentOS 7/EPEL system today - I believe this should work everywhere except CentOS 6. Ahh, it doesn't work on CentOS 7, because firewalld is version 0.9.7 there. Any chance of updating the EPEL 7 branch to 0.10? That'd also bring IPv6 support, which would be good. BTW: in my last comment that should be "because fail2ban is version 0.9.7" (not firewalld - too many Fs). It does look like the following works okay in fail2ban-0.9.7, so even if the version isn't updated, the fail2ban-firewalld subpackage could be updated with it: banaction = firewallcmd-ipset banaction_allports = firewallcmd-ipset FEDORA-2019-e779b23681 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-e779b23681 FEDORA-2019-1a35bad958 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-1a35bad958 FEDORA-EPEL-2019-dac149ad76 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-dac149ad76 fail2ban-0.10.4-8.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-e779b23681 fail2ban-0.10.4-1.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-dac149ad76 fail2ban-0.10.4-8.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-1a35bad958 fail2ban-0.10.4-8.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report. fail2ban-0.10.4-8.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report. fail2ban-0.10.4-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report. |