You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed today, that the output from the fail2ban script is a bit weired:
root@mail:/# fail2ban
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
Banned in postfix-sasl:
Banned in postfix-sasl:
Banned in postfix-sasl: 58.57.4.238
Banned in postfix-sasl:
iptables: No chain/target/match by that name.
Banned in sshd:
Banned in sshd:
Banned in sshd: 58.57.4.238
Banned in sshd:
As you can see, only one IP is blocked in the f2b-postfix-sasl chain.
However the script reports a lot of empty lines "Banned in " + also falsely reports the IP banned in the sshd chain.
I copied over the version before the refactoring #1654, which outputs correctly:
root@mail:/# bash fail2ban.old
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
Banned in postfix-sasl: 58.57.4.238
iptables: No chain/target/match by that name.
What is affected by this bug?
/usr/local/bin/fail2ban
When does this occur?
always
Actual Behavior
Incorrect output
Expected behavior (i.e. solution)
Same output as before the refactoring.
Solution
None yet. I will take a closer look by the end of the week. @aendeavor do you have an idea what could be the cause?
The text was updated successfully, but these errors were encountered:
Context
I noticed today, that the output from the fail2ban script is a bit weired:
My iptables at the time:
As you can see, only one IP is blocked in the f2b-postfix-sasl chain.
However the script reports a lot of empty lines "Banned in " + also falsely reports the IP banned in the sshd chain.
I copied over the version before the refactoring #1654, which outputs correctly:
What is affected by this bug?
/usr/local/bin/fail2ban
When does this occur?
always
Actual Behavior
Incorrect output
Expected behavior (i.e. solution)
Same output as before the refactoring.
Solution
None yet. I will take a closer look by the end of the week. @aendeavor do you have an idea what could be the cause?
The text was updated successfully, but these errors were encountered: