#2 iptables -l not showing fail2ban chain

[Jair]

Hello fail2ban maintainers,

I write just to indicate that the program seems to be working as expected, my system is a Lenovo X1 laptop running Ubuntu 20.04 LTS with fail2ban version:

$ sudo fail2ban-client --version
Fail2Ban v0.11.1

My curiosity is that when running the command:

sudo iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         
ACCEPT     udp  --  anywhere             anywhere             multiport dports mdns
ACCEPT     tcp  --  anywhere             anywhere             multiport dports 4000

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination 

I don't see the new chain added? However, the software seems to be working as I tested the ban features.

I have this in the default configuration file:

$ less jail.local | grep iptables
# ssh-iptables jail the following (uncommented) would appear in the .local file.
# Default banning action (e.g. iptables, iptables-new,
# iptables-multiport, shorewall, etc) It is used to define
banaction = iptables-multiport
banaction_allports = iptables-allports
action = iptables-allports[name=NoAuthFailures]
# ports such as iptables-allports, shorewall
banaction = iptables-multiport-log

Thank you in advance for having a look at this.

Sincerely,

[Serg G. Brester]

Due to support of IPv6 and other reasons, in new version banactions will execute actionstart on demand (by first ban of IP for corresponding family).
See https://github.com/fail2ban/fail2ban/issues/1755#issuecomment-295286513 for more details.

[Jair]

Hello Serg,

Thanks for the prompt answer, I will keep looking at fail2ban and the IPv6 progress.

I appreciate all your team do.

Sincerely,