Bug#1053414: fail2ban: Creates the chain in iptables but does not add the banned IPs.

2024-09-01 Thread Christoph Anton Mitterer
Hey. Yes, one can expect, that people know which firewall they use, but not that fail2ban rather silently switches from previously iptables to nftables. Especially also as fail2ban seems to fail silently (I'm mean it's in the logs, but one cannot really expect people to read them without reason)

Bug#1053414: fail2ban: Creates the chain in iptables but does not add the banned IPs.

2024-08-31 Thread Sylvestre Ledru
Hello, Not sure I agree with the change of severity. If you are using such tools, you should know which firewall you have installed. What do you think we should do ? for the install of nftables? Thanks S Le 31/08/2024 à 02:01, Christoph Anton Mitterer a écrit : Control: severity -1 grave

Bug#1053414: fail2ban: Creates the chain in iptables but does not add the banned IPs.

2024-08-30 Thread Christoph Anton Mitterer
Control: severity -1 grave Hey. I'd say this one is also at least grave (it breaks the sensible use of fail2ban itself) or rather even critical (as fail2ban is used for security purposes). The package recommends either iptables/nftalbes (which I guess is in principle good, because people should

Bug#1053414: fail2ban: Creates the chain in iptables but does not add the banned IPs.

2023-10-03 Thread Bruno Meirelles
Package: fail2ban X-Debbugs-Cc: bmeirel...@gmail.com Version: 1.0.2-2 Severity: important Dear Maintainer, He creates the chain in iptables, but doesn't add the banned IPs. I switched to using nftables, and it's working correctly." -- System Information: Debian Release: 12.1   APT prefers sta