Fail2ban nie blokuje ip

Konfiguracja serwerów, usług, itp.
bilivj
Posty: 25
Rejestracja: 11 lutego 2014, 18:16

[+]Fail2ban nie blokuje ip

Post autor: bilivj »

Witam
Mam problem z fail2ban.
Narzędzie nie działa, nie blokuje ip po określeniu ilości nieudanych prób logowań.

Zainstalowałem poprzez:

Kod: Zaznacz cały

[color=#000000][font=Courier New][I]apt-get install fail2ban[/I][/font][/color]
Następnie utworzyłem plik: jail.local w a nim

Kod: Zaznacz cały

[pureftpd]
enabled  = true
port     = ftp
filter   = pureftpd
logpath  = /var/log/syslog
maxretry = 3


#[dovecot-pop3imap]
#enabled = true
#filter = dovecot-pop3imap
#action = iptables-multiport[name=dovecot-pop3imap, port="pop3,pop3s,imap,imaps", protocol=tcp]
#logpath = /var/log/mail.log
#maxretry = 5


[postfix-sasl]
enabled  = true
port     = smtp
filter   = postfix-sasl
logpath  = /var/log/mail.log
maxretry = 3    




[dovecot-pop3imap]
enabled = true
filter = dovecot-pop3imap
port = pop3,pop3s,imap,imaps
action = iptables-multiport[name=dovecot-pop3imap, port="pop3,pop3s,imap,imaps", protocol=tcp]
# optionaly mail notification # mail[name=dovecot-pop3imap, dest=root@domain] # see /etc/fail2ban/action.d/ or Fail2Ban doc
logpath = /var/log/mail.log
maxretry = 5
findtime = 1200
bantime = 604800
Filtr

Kod: Zaznacz cały

[Definition]failregex = (?: pop3-login|imap-login): .*(?:Authentication failure|Aborted login \(auth failed|Aborted login \(tried to use disabled|Disconnected \(auth failed|Aborted login \(\d+ authentication attempts).*rip=(?P<host>\S*),.*
ignoreregex =


Niestety nie są blokowane adresy ip po nieudanych pięciu błędnych próbach logowań.
Co robię nie tak?

Dorzucam jeszcze plik jail.conf

Kod: Zaznacz cały

# Fail2Ban configuration file.#
# This file was composed for Debian systems from the original one
# provided now under /usr/share/doc/fail2ban/examples/jail.conf
# for additional examples.
#
# Comments: use '#' for comment lines and ';' for inline comments
#
# To avoid merges during upgrades DO NOT MODIFY THIS FILE
# and rather provide your changes in /etc/fail2ban/jail.local
#


# The DEFAULT allows a global definition of the options. They can be overridden
# in each jail afterwards.


[DEFAULT]


# "ignoreip" can be an IP address, a CIDR mask or a DNS host. Fail2ban will not
# ban a host which matches an address in this list. Several addresses can be
# defined using space separator.
ignoreip = 127.0.0.1/8


# External command that will take an tagged arguments to ignore, e.g. <ip>,
# and return true if the IP is to be ignored. False otherwise.
#
# ignorecommand = /path/to/command <ip>
ignorecommand =


# "bantime" is the number of seconds that a host is banned.
bantime  = 600


# A host is banned if it has generated "maxretry" during the last "findtime"
# seconds.
findtime = 600
maxretry = 3


# "backend" specifies the backend used to get files modification.
# Available options are "pyinotify", "gamin", "polling" and "auto".
# This option can be overridden in each jail as well.
#
# pyinotify: requires pyinotify (a file alteration monitor) to be installed.
#            If pyinotify is not installed, Fail2ban will use auto.
# gamin:     requires Gamin (a file alteration monitor) to be installed.
#            If Gamin is not installed, Fail2ban will use auto.
# polling:   uses a polling algorithm which does not require external libraries.
# auto:      will try to use the following backends, in order:
#            pyinotify, gamin, polling.
backend = auto


# "usedns" specifies if jails should trust hostnames in logs,
#   warn when reverse DNS lookups are performed, or ignore all hostnames in logs
#
# yes:   if a hostname is encountered, a reverse DNS lookup will be performed.
# warn:  if a hostname is encountered, a reverse DNS lookup will be performed,
#        but it will be logged as a warning.
# no:    if a hostname is encountered, will not be used for banning,
#        but it will be logged as info.
usedns = warn


#
# Destination email address used solely for the interpolations in
# jail.{conf,local} configuration files.
destemail = root@localhost


#
# Name of the sender for mta actions
sendername = Fail2Ban


# Email address of the sender
sender = fail2ban@localhost


#
# ACTIONS
#


# Default banning action (e.g. iptables, iptables-new,
# iptables-multiport, shorewall, etc) It is used to define
# action_* variables. Can be overridden globally or per
# section within jail.local file
banaction = iptables-multiport


# email action. Since 0.8.1 upstream fail2ban uses sendmail
# MTA for the mailing. Change mta configuration parameter to mail
# if you want to revert to conventional 'mail'.
mta = sendmail


# Default protocol
protocol = tcp


# Specify chain where jumps would need to be added in iptables-* actions
chain = INPUT


#
# Action shortcuts. To be used to define action parameter


# The simplest action to take: ban only
action_ = %(banaction)s[name=%(__name__)s, port="%(port)s", protocol="%(protocol)s", chain="%(chain)s"]


# ban & send an e-mail with whois report to the destemail.
action_mw = %(banaction)s[name=%(__name__)s, port="%(port)s", protocol="%(protocol)s", chain="%(chain)s"]
              %(mta)s-whois[name=%(__name__)s, dest="%(destemail)s", protocol="%(protocol)s", chain="%(chain)s", sendername="%(sendername)s"]


# ban & send an e-mail with whois report and relevant log lines
# to the destemail.
action_mwl = %(banaction)s[name=%(__name__)s, port="%(port)s", protocol="%(protocol)s", chain="%(chain)s"]
               %(mta)s-whois-lines[name=%(__name__)s, dest="%(destemail)s", logpath=%(logpath)s, chain="%(chain)s", sendername="%(sendername)s"]


# Choose default action.  To change, just override value of 'action' with the
# interpolation to the chosen action shortcut (e.g.  action_mw, action_mwl, etc) in jail.local
# globally (section [DEFAULT]) or per specific section
action = %(action_)s


#
# JAILS
#


# Next jails corresponds to the standard configuration in Fail2ban 0.6 which
# was shipped in Debian. Enable any defined here jail by including
#
# [SECTION_NAME]
# enabled = true


#
# in /etc/fail2ban/jail.local.
#
# Optionally you may override any other parameter (e.g. banaction,
# action, port, logpath, etc) in that section within jail.local


[ssh]


enabled  = true
port     = ssh
filter   = sshd
logpath  = /var/log/auth.log
maxretry = 6


[dropbear]


enabled  = false
port     = ssh
filter   = dropbear
logpath  = /var/log/auth.log
maxretry = 6


# Generic filter for pam. Has to be used with action which bans all ports
# such as iptables-allports, shorewall
[pam-generic]


enabled  = false
# pam-generic filter can be customized to monitor specific subset of 'tty's
filter   = pam-generic
# port actually must be irrelevant but lets leave it all for some possible uses
port     = all
banaction = iptables-allports
port     = anyport
logpath  = /var/log/auth.log
maxretry = 6


[xinetd-fail]


enabled   = false
filter    = xinetd-fail
port      = all
banaction = iptables-multiport-log
logpath   = /var/log/daemon.log
maxretry  = 2




[ssh-ddos]


enabled  = false
port     = ssh
filter   = sshd-ddos
logpath  = /var/log/auth.log
maxretry = 6




# Here we use blackhole routes for not requiring any additional kernel support
# to store large volumes of banned IPs


[ssh-route]


enabled = false
filter = sshd
action = route
logpath = /var/log/sshd.log
maxretry = 6


# Here we use a combination of Netfilter/Iptables and IPsets
# for storing large volumes of banned IPs
#
# IPset comes in two versions. See ipset -V for which one to use
# requires the ipset package and kernel support.
[ssh-iptables-ipset4]


enabled  = false
port     = ssh
filter   = sshd
banaction = iptables-ipset-proto4
logpath  = /var/log/sshd.log
maxretry = 6


[ssh-iptables-ipset6]


enabled  = false
port     = ssh
filter   = sshd
banaction = iptables-ipset-proto6
logpath  = /var/log/sshd.log
maxretry = 6




#
# HTTP servers
#


[apache]


enabled  = false
port     = http,https
filter   = apache-auth
logpath  = /var/log/apache*/*error.log
maxretry = 6


# default action is now multiport, so apache-multiport jail was left
# for compatibility with previous (<0.7.6-2) releases
[apache-multiport]


enabled   = false
port      = http,https
filter    = apache-auth
logpath   = /var/log/apache*/*error.log
maxretry  = 6


[apache-noscript]


enabled  = false
port     = http,https
filter   = apache-noscript
logpath  = /var/log/apache*/*error.log
maxretry = 6


[apache-overflows]


enabled  = false
port     = http,https
filter   = apache-overflows
logpath  = /var/log/apache*/*error.log
maxretry = 2


[apache-modsecurity]


enabled  = false
filter   = apache-modsecurity
port     = http,https
logpath  = /var/log/apache*/*error.log
maxretry = 2


[apache-nohome]


enabled  = false
filter   = apache-nohome
port     = http,https
logpath  = /var/log/apache*/*error.log
maxretry = 2


# Ban attackers that try to use PHP's URL-fopen() functionality
# through GET/POST variables. - Experimental, with more than a year
# of usage in production environments.


[php-url-fopen]


enabled = false
port    = http,https
filter  = php-url-fopen
logpath = /var/www/*/logs/access_log


# A simple PHP-fastcgi jail which works with lighttpd.
# If you run a lighttpd server, then you probably will
# find these kinds of messages in your error_log:
#   ALERT – tried to register forbidden variable ‘GLOBALS’
#   through GET variables (attacker '1.2.3.4', file '/var/www/default/htdocs/index.php')


[lighttpd-fastcgi]


enabled = false
port    = http,https
filter  = lighttpd-fastcgi
logpath = /var/log/lighttpd/error.log


# Same as above for mod_auth
# It catches wrong authentifications


[lighttpd-auth]


enabled = false
port    = http,https
filter  = suhosin
logpath = /var/log/lighttpd/error.log


[nginx-http-auth]


enabled = false
filter  = nginx-http-auth
port    = http,https
logpath = /var/log/nginx/error.log


# Monitor roundcube server


[roundcube-auth]


enabled  = false
filter   = roundcube-auth
port     = http,https
logpath  = /var/log/roundcube/userlogins




[sogo-auth]


enabled  = false
filter   = sogo-auth
port     = http, https
# without proxy this would be:
# port    = 20000
logpath  = /var/log/sogo/sogo.log




#
# FTP servers
#


[vsftpd]


enabled  = false
port     = ftp,ftp-data,ftps,ftps-data
filter   = vsftpd
logpath  = /var/log/vsftpd.log
# or overwrite it in jails.local to be
# logpath = /var/log/auth.log
# if you want to rely on PAM failed login attempts
# vsftpd's failregex should match both of those formats
maxretry = 6




[proftpd]


enabled  = false
port     = ftp,ftp-data,ftps,ftps-data
filter   = proftpd
logpath  = /var/log/proftpd/proftpd.log
maxretry = 6




[pure-ftpd]


enabled  = false
port     = ftp,ftp-data,ftps,ftps-data
filter   = pure-ftpd
logpath  = /var/log/syslog
maxretry = 6




[wuftpd]


enabled  = false
port     = ftp,ftp-data,ftps,ftps-data
filter   = wuftpd
logpath  = /var/log/syslog
maxretry = 6




#
# Mail servers
#


[postfix]


enabled  = false
port     = smtp,ssmtp,submission
filter   = postfix
logpath  = /var/log/mail.log




[couriersmtp]


enabled  = false
port     = smtp,ssmtp,submission
filter   = couriersmtp
logpath  = /var/log/mail.log




#
# Mail servers authenticators: might be used for smtp,ftp,imap servers, so
# all relevant ports get banned
#


[courierauth]


enabled  = false
port     = smtp,ssmtp,submission,imap2,imap3,imaps,pop3,pop3s
filter   = courierlogin
logpath  = /var/log/mail.log




[sasl]


enabled  = false
port     = smtp,ssmtp,submission,imap2,imap3,imaps,pop3,pop3s
filter   = postfix-sasl
# You might consider monitoring /var/log/mail.warn instead if you are
# running postfix since it would provide the same log lines at the
# "warn" level but overall at the smaller filesize.
logpath  = /var/log/mail.log


[dovecot]


enabled = false
port    = smtp,ssmtp,submission,imap2,imap3,imaps,pop3,pop3s
filter  = dovecot
logpath = /var/log/mail.log


# To log wrong MySQL access attempts add to /etc/my.cnf:
# log-error=/var/log/mysqld.log
# log-warning = 2
[mysqld-auth]


enabled  = false
filter   = mysqld-auth
port     = 3306
logpath  = /var/log/mysqld.log




# DNS Servers




# These jails block attacks against named (bind9). By default, logging is off
# with bind9 installation. You will need something like this:
#
# logging {
#     channel security_file {
#         file "/var/log/named/security.log" versions 3 size 30m;
#         severity dynamic;
#         print-time yes;
#     };
#     category security {
#         security_file;
#     };
# };
#
# in your named.conf to provide proper logging


# !!! WARNING !!!
#   Since UDP is connection-less protocol, spoofing of IP and imitation
#   of illegal actions is way too simple.  Thus enabling of this filter
#   might provide an easy way for implementing a DoS against a chosen
#   victim. See
#    http://nion.modprobe.de/blog/archives/690-fail2ban-+-dns-fail.html
#   Please DO NOT USE this jail unless you know what you are doing.
#[named-refused-udp]
#
#enabled  = false
#port     = domain,953
#protocol = udp
#filter   = named-refused
#logpath  = /var/log/named/security.log


[named-refused-tcp]


enabled  = false
port     = domain,953
protocol = tcp
filter   = named-refused
logpath  = /var/log/named/security.log


[freeswitch]


enabled  = false
filter   = freeswitch
logpath  = /var/log/freeswitch.log
maxretry = 10
action   = iptables-multiport[name=freeswitch-tcp, port="5060,5061,5080,5081", protocol=tcp]
           iptables-multiport[name=freeswitch-udp, port="5060,5061,5080,5081", protocol=udp]


[ejabberd-auth]


enabled  = false
filter   = ejabberd-auth
port     = xmpp-client
protocol = tcp
logpath  = /var/log/ejabberd/ejabberd.log




# Multiple jails, 1 per protocol, are necessary ATM:
# see https://github.com/fail2ban/fail2ban/issues/37
[asterisk-tcp]


enabled  = false
filter   = asterisk
port     = 5060,5061
protocol = tcp
logpath  = /var/log/asterisk/messages


[asterisk-udp]


enabled  = false
filter     = asterisk
port     = 5060,5061
protocol = udp
logpath  = /var/log/asterisk/messages




# Jail for more extended banning of persistent abusers
# !!! WARNING !!!
#   Make sure that your loglevel specified in fail2ban.conf/.local
#   is not at DEBUG level -- which might then cause fail2ban to fall into
#   an infinite loop constantly feeding itself with non-informative lines
[recidive]


enabled  = false
filter   = recidive
logpath  = /var/log/fail2ban.log
action   = iptables-allports[name=recidive]
           sendmail-whois-lines[name=recidive, logpath=/var/log/fail2ban.log]
bantime  = 604800  ; 1 week
findtime = 86400   ; 1 day
maxretry = 5


# See the IMPORTANT note in action.d/blocklist_de.conf for when to
# use this action
#
# Report block via blocklist.de fail2ban reporting service API
# See action.d/blocklist_de.conf for more information
[ssh-blocklist]


enabled  = false
filter   = sshd
action   = iptables[name=SSH, port=ssh, protocol=tcp]
           sendmail-whois[name=SSH, dest="%(destemail)s", sender="%(sender)s", sendername="%(sendername)s"]
           blocklist_de[email="%(sender)s", apikey="xxxxxx", service="%(filter)s"]
logpath  = /var/log/sshd.log
maxretry = 20




# consider low maxretry and a long bantime
# nobody except your own Nagios server should ever probe nrpe
[nagios]
enabled  = false
filter   = nagios
action   = iptables[name=Nagios, port=5666, protocol=tcp]
           sendmail-whois[name=Nagios, dest="%(destemail)s", sender="%(sender)s", sendername="%(sendername)s"]
logpath  = /var/log/messages     ; nrpe.cfg may define a different log_facility
maxretry = 1


Sprawdzam czy ip są blokowane wywołując komendę: iptables -nL
Awatar użytkownika
pawkrol
Moderator
Posty: 939
Rejestracja: 03 kwietnia 2011, 10:25

Post autor: pawkrol »

Ja korzystam z takiego filtra spróbuj:

Kod: Zaznacz cały

# Fail2Ban filter Dovecot authentication and pop3/imap server
#

[INCLUDES]

before = common.conf
[Definition]
_daemon = (auth|dovecot(-auth)?|auth-worker)
failregex = ^%(__prefix_line)s(pam_unix(\(dovecot:auth\))? :) ?\s+authentication failure; logname=\S* uid=\S* euid=\S* tty=dovecot ruser=\S* rhost=<HOST>(\s+user=\S*)?\s*$
            ^%(__prefix_line)s(pop3|imap)-login: (Info: )?(Aborted login|Disconnected)(: Inactivity)? \(((auth failed, \d+ attempts)( in \d+ secs)?|tried to use (disabled|disallowed) \S+ auth)\) :( user=<\S*>,)?( method=\S+,)? rip=<HOST>(, lip=(\d{1,3}\.){3}\d{1,3})?(, TLS( handshaking(: SSL_accept\(\) failed: error:[\dA-F]+:SSL routines:[TLS\d]+_GET_CLIENT_HELLO:unknown protocol)?)?(: Disconnected)?)?(, session=<\S+>)?\s*$
            ^%(__prefix_line)s(Info|dovecot: auth\(default\)): pam\(\S+,<HOST>\): pam_authenticate\(\) failed: (User not known to the underlying authentication module: \d+ Time\(s\)|Authentication failure \(password mismatch\?\))\s*$
ignoreregex = 
bilivj
Posty: 25
Rejestracja: 11 lutego 2014, 18:16

Post autor: bilivj »

Wrzucone. Zobaczę czy działa.
W jaki sposób mogę przetestować jakoś czy działa ten fail2ban w ogóle?
Awatar użytkownika
pawkrol
Moderator
Posty: 939
Rejestracja: 03 kwietnia 2011, 10:25

Post autor: pawkrol »

Spróbuj się błędnie pologować po ssh. Widzę że masz włączone

Kod: Zaznacz cały

[ssh]  
enabled  = true 
port     = ssh 
filter   = sshd
logpath  = /var/log/auth.log 
maxretry = 6
bilivj
Posty: 25
Rejestracja: 11 lutego 2014, 18:16

Post autor: bilivj »

Przetestowałem dla ssh i działa, ip trafia na listę. Brak dostępu do serwera wtedy.
Poczekam co będzie z tym nowym filtrem.
Jak na złość w logach póki co cisza.

Dodane:

Sprawdziłem i przybyło wpisów w logach, niestety adres nie został zablokowany.
czyli wychodzi na to, że nie działa nadal dla poczty.

Wpisy w logach typu:

Kod: Zaznacz cały

postfix/smtpd[5522]: warning: unknown[xxx.xxx.xxx.xxx]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Może nie jest brany pod uwagę plik jail.local gdzie wrzucam te dodane reguły?
Jak to sprawdzić?

Log fail2ban.log też nie wskazuje żadnych błędów.
Awatar użytkownika
pawkrol
Moderator
Posty: 939
Rejestracja: 03 kwietnia 2011, 10:25

Post autor: pawkrol »

To jest log z pliku /var/log/dovecot.log? Bo coś mi się nie widzi.
Ponadto nie zadziała to co Ci dałem, gdyż jak widzisz filtr nie pasuje do komunikatu.

Bardziej ten :

Kod: Zaznacz cały

[sasl]
enabled  = true
port     = smtp,ssmtp,submission,imap2,imap3,imaps,pop3,pop3s
filter   = postfix-sasl
logpath  = /var/log/mail.log
bilivj
Posty: 25
Rejestracja: 11 lutego 2014, 18:16

Post autor: bilivj »

Nie to nie jest dovecot.log bo takiego jako tako nie mam.
Myślałem, że to ten log odpowiada za to.

Wrzucam dłuższy fragment tego logu:

Kod: Zaznacz cały

Oct 27 09:15:02 vpsaaaaaa postfix/smtpd[8951]: disconnect from localhost[127.0.0.1]Oct 27 09:15:02 vpsaaaaaa dovecot: pop3-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, secured, session=<ndK0rBEjIgB/AAAB>
Oct 27 09:20:02 vpsaaaaaa dovecot: imap-login: Disconnected (disconnected before auth was ready, waited 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, secured, session=<fJySvhEjWAB/AAAB>
Oct 27 09:20:02 vpsaaaaaa dovecot: pop3-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, secured, session=<cMqTvhEj+AB/AAAB>
Oct 27 09:20:02 vpsaaaaaa postfix/smtpd[9062]: connect from localhost[127.0.0.1]
Oct 27 09:20:02 vpsaaaaaa postfix/smtpd[9062]: lost connection after CONNECT from localhost[127.0.0.1]
Oct 27 09:20:02 vpsaaaaaa postfix/smtpd[9062]: disconnect from localhost[127.0.0.1]
Oct 27 09:21:57 vpsaaaaaa postfix/smtpd[9100]: connect from unknown[5.8.66.239]
Oct 27 09:21:59 vpsaaaaaa postfix/smtpd[9100]: warning: unknown[5.8.66.239]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct 27 09:21:59 vpsaaaaaa postfix/smtpd[9100]: lost connection after AUTH from unknown[5.8.66.239]
Oct 27 09:21:59 vpsaaaaaa postfix/smtpd[9100]: disconnect from unknown[5.8.66.239]
Oct 27 09:25:02 vpsaaaaaa dovecot: imap-login: Disconnected (disconnected before auth was ready, waited 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, secured, session=<k/V90BEjEgB/AAAB>
Oct 27 09:25:02 vpsaaaaaa postfix/smtpd[9169]: connect from localhost[127.0.0.1]
Oct 27 09:25:02 vpsaaaaaa postfix/smtpd[9169]: lost connection after CONNECT from localhost[127.0.0.1]
Oct 27 09:25:02 vpsaaaaaa postfix/smtpd[9169]: disconnect from localhost[127.0.0.1]
Oct 27 09:25:02 vpsaaaaaa dovecot: pop3-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, secured, session=<pz5/0BEjsgB/AAAB>

Aktywowałem wspomniany filtr w jail.conf. Można robić to w conf czy powinno się w local?

Włączone:

Kod: Zaznacz cały

[sasl]

enabled  = true
port     = smtp,ssmtp,submission,imap2,imap3,imaps,pop3,pop3s
filter   = postfix-sasl
# You might consider monitoring /var/log/mail.warn instead if you are
# running postfix since it would provide the same log lines at the
# "warn" level but overall at the smaller filesize.
logpath  = /var/log/mail.log
maxretry = 3


[dovecot]


enabled = true
port    = smtp,ssmtp,submission,imap2,imap3,imaps,pop3,pop3s
filter  = dovecot
logpath = /var/log/mail.log
maxretry = 3
Wrzucić filtry do tych dwóch powyższych? Są to standardowe filtry od fail2ban.
Awatar użytkownika
pawkrol
Moderator
Posty: 939
Rejestracja: 03 kwietnia 2011, 10:25

Post autor: pawkrol »

W local dawałbym własne blokady.
W conf masz już kilka wstępnie zdefiniowanych, więc wystarczy je tylko włączyć.

Ponadto jak nie masz dovecota to po co włączasz ten filtr?
bilivj
Posty: 25
Rejestracja: 11 lutego 2014, 18:16

[+]Fail2ban nie blokuje ip

Post autor: bilivj »

Sugerowałem się wpisami w logach, którego fragment wrzuciłem w poprzednim poście.
Włączyłem również ten filtr ponieważ odwołuje się on do tego samego pliku logów.

Edit
Nadal nie działa.
Czytam, testuję kolejne filtry i nic.
Znalazłem informację polecenie:

Kod: Zaznacz cały

fail2ban-regex /ścieżka_logu /ścieżka_filtra
i testując różne filtry żaden nie działa.
Nie wiem kompletnie co myśleć, dlaczego to nie działa.

Sprawa rozwiązana.
Problemem były błędne filtry raz mały czas findtime.
ODPOWIEDZ