New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shorewall doesn't start after fail2ban install #6608
Comments
gsanchietti
added a commit
to NethServer/nethserver-fail2ban
that referenced
this issue
Dec 3, 2021
If the ipset are not created, shorewall may fail at boot with: shorewall[989]: WARNING: Ipset f2b-asterisk-tcp does not exist /etc/shorewall/blrules (line 30) shorewall[989]: WARNING: Ipset f2b-asterisk-udp does not exist /etc/shorewall/blrules (line 31) NethServer/dev#6608
Test case |
Test case verified. |
nrauso
added
verified
All test cases were verified successfully
and removed
testing
Packages are available from testing repositories
labels
Dec 3, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On a machine with
asterisk
installed, shorewall doesn't start after the machine reboot.This affect only newly installed machines, not updated ones.
Steps to reproduce
yum install @nethserver-pbx
yum install nethserver-fail2ban
Expected behavior
After the boot, shorewall should be up&running.
Actual behavior
Shorewall is stopped.
This is a regression caused by #6605
Components
nethserver-fail2ban-1.7.2-1.ns7.noarch
Thanks to @nrauso and @francio87
The text was updated successfully, but these errors were encountered: