Fail2ban: Difference between revisions
From DWIKI
m (→FAQ) |
m (→FAQ) |
||
Line 33: | Line 33: | ||
==unban an IP== | ==unban an IP== | ||
fail2ban-client set <jailname> unbanip <bannedip> | fail2ban-client set <jailname> unbanip <bannedip> | ||
==sshd rule not working on Ubuntu 20.04== | |||
Probably silently fails on missing pyinotify | |||
apt install inotify-tools inotify-hookable python-pyinotify | |||
OR change backend: | |||
sshd_backend = systemd | |||
(not working??) |
Revision as of 13:29, 15 April 2022
Links
Custom rules
assp.conf
failregex = \[Worker_.*\] <HOST> \[SMTP Error\] 535 5.7.8 Error: authentication failed: \[Worker_.*\] \[SSL-in\] \[TLS-out\] <HOST> \[SMTP Error\] 535 \[Worker_.*\] \[MessageLimit\] <HOST> \[Worker_.*\] <HOST> .* \[SMTP Error\] 554 5.7.1
FAQ
Error in FilterPyinotify callback: 'module' object has no attribute '_strptime_time'
Enabling sshd-ddos filter seems to trigger this
WARNING Unable to find a corresponding IP address for client: (-2, 'Name or service not known')
Crap code, maybe look at usedns in fail.conf
test filter
fail2ban-regex /usr/share/assp/logs/maillog.txt /etc/fail2ban/filter.d/assp.conf
I don't see the rules
Maybe its using ipset, check
ipset list
unban an IP
fail2ban-client set <jailname> unbanip <bannedip>
sshd rule not working on Ubuntu 20.04
Probably silently fails on missing pyinotify
apt install inotify-tools inotify-hookable python-pyinotify
OR change backend:
sshd_backend = systemd
(not working??)