After updating from 4.211.64-4 to 5.211.65-10 (ran the upgrade scripts one at a time reboot between each) we seem to have an issue with our fail2ban. The web GUI shows it as not running and when I run and iptables -L it only get back a few lines (see below) as appose to what is normal.
Any suggestion on how to restore the fail2ban back to normal?
I already tried to uninstall iptables and reinstall, that seem to break everything possible forcing me to restore for a backup.
What I get now:
iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
What I get with a working system:
iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
fail2ban-FTP tcp – anywhere anywhere
fail2ban-BadBots tcp – anywhere anywhere
fail2ban-PBX-GUI tcp – anywhere anywhere
fail2ban-SIP all – anywhere anywhere
fail2ban-SSH tcp – anywhere anywhere
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain fail2ban-BadBots (1 references)
target prot opt source destination
RETURN all – anywhere anywhere
Chain fail2ban-FTP (1 references)
target prot opt source destination
RETURN all – anywhere anywhere
Chain fail2ban-PBX-GUI (1 references)
target prot opt source destination
RETURN all – anywhere anywhere
Chain fail2ban-SIP (1 references)
target prot opt source destination
RETURN all – anywhere anywhere
Chain fail2ban-SSH (1 references)
target prot opt source destination
RETURN all – anywhere anywhere