Fail2Ban DROP instead REJECT
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
|#Depending on version one of the following files must exist|
|root@host:/ nano /etc/fail2ban/action.d/iptables-blocktype.conf|
|root@host:/ nano /etc/fail2ban/action.d/iptables-common.conf|
|comment the line|
|#blocktype = REJECT --reject-with icmp-port-unreachable|
|create the line|
|blocktype = DROP|
Jan 10, 2021
I think REJECT is very strange choice for default.
I've realize it when found a lot of ICMP traffic from me. It customizes easy, but a lot of people will not change it.
I've read #507 and I'm not agree.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Status for the jail: sshd
| |- Currently failed: 0
| |- Total failed: 95097
- Journal matches: _SYSTEMD_UNIT=sshd.service + _COMM=sshd- Actions
|- Currently banned: 483
|- Total banned: 1785
DROP, REJECT, Same fight. I don't understand why connection attempts continue while IP addresses are banned.
root (220.127.116.11): 45 Time(s)
root (18.104.22.168): 45 Time(s)
root (22.214.171.124): 45 Time(s)
root (126.96.36.199): 45 Time(s)
root (188.8.131.52): 45 Time(s)
root (184.108.40.206): 45 Time(s)
root (220.127.116.11): 45 Time(s)
Does anyone have any idea?