It looks like fail2ban also installs nftable, and the nftable rules are what is doing the blocking. Once fail2ban is uninstalled nftable is also uninstalled and the rules are removed.
I have started a discussion on the fail2ban github site, and will follow up there: https://github.com/fail2ban/fail2ban/discussions/4210 Thanks for the help. On Fri, Jul 17, 2026, at 4:44 PM, Marco Moock wrote: > Am 17.07.26 um 21:36 schrieb Tom Moore via Fail2ban-users: > > > > Does anyone have an idea of what is going wrong here? If seems to work ok > > initially, but after the first reboot the port is blocked. Ssh still > > works, so it is not like all ports are blocked. I do notice that some of > > the aws ec2 monitoring is not reporting, so perhaps other ports are blocked > > as well. > > Do you have a firewall installed? > Enable logging there and check the logs. > Fedora comes with firewalld by default. > > > -- > Gruß > Marco > > Junk-Mail bitte an [email protected] > > _______________________________________________ > Fail2ban-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/fail2ban-users > > > *Attachments:* > • OpenPGP_signature.asc -- Tom Moore Spatial Planning Systems 960 Burkes Bluff Lane Deep River ON K0J 1P0 Canada Phone: +1 613 584 9354
_______________________________________________ Fail2ban-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fail2ban-users
