fail2ban self blocked IPs not showing up on VestaCP
Posted: Tue Sep 27, 2016 8:22 pm
this is part of my iptables -L -n
I'm noticing that my manual blocks through Vesta, have chain names fail2ban-filter, while the fail2ban service itself adds actions named f2b-filter to iptables.
I think this is the reason why I can't see the chains added by ip2tables through the Vesta Control Panel.
Is this intentional or a bug?
Code: Select all
Chain f2b-SSH (1 references)
target prot opt source destination
REJECT all -- 193.201.225.122 0.0.0.0/0 reject-with icmp-port-unreachable
REJECT all -- 221.194.47.229 0.0.0.0/0 reject-with icmp-port-unreachable
REJECT all -- 221.194.47.208 0.0.0.0/0 reject-with icmp-port-unreachable
REJECT all -- 121.18.238.109 0.0.0.0/0 reject-with icmp-port-unreachable
REJECT all -- 119.249.54.66 0.0.0.0/0 reject-with icmp-port-unreachable
REJECT all -- 116.31.116.10 0.0.0.0/0 reject-with icmp-port-unreachable
RETURN all -- 0.0.0.0/0 0.0.0.0/0
Chain f2b-dovecot (1 references)
target prot opt source destination
RETURN all -- 0.0.0.0/0 0.0.0.0/0
Chain f2b-exim (1 references)
target prot opt source destination
RETURN all -- 0.0.0.0/0 0.0.0.0/0
Chain fail2ban-MAIL (1 references)
target prot opt source destination
REJECT all -- 121.73.98.209 0.0.0.0/0 reject-with icmp-port-unreachable
REJECT all -- 155.133.82.141 0.0.0.0/0 reject-with icmp-port-unreachable
RETURN all -- 0.0.0.0/0 0.0.0.0/0
Chain fail2ban-SSH (1 references)
target prot opt source destination
REJECT all -- 221.194.47.0 0.0.0.0/0 reject-with icmp-port-unreachable
REJECT all -- 116.31.116.10 0.0.0.0/0 reject-with icmp-port-unreachable
RETURN all -- 0.0.0.0/0 0.0.0.0/0
I think this is the reason why I can't see the chains added by ip2tables through the Vesta Control Panel.
Is this intentional or a bug?