No idea. Built-in in the Imm firmware. Just partial screenshot from imm web gui

Fail2ban does not listen on any port for it has no user interface. No interface at all actually. It’s just a process that monitors your logfiles and changes firewall rules and writes to syslog if you tell it to.

I run it on internet facing servers so I use a ‘regular’ install and never docker. I see no advantage for docker in this case, but one huge disadvantage: Docker changes a lot on the network side. It creates bridges, and picks IP’s all by itself. I hate that. (I know you can put in a lot of effort to manage it, but no thanks keep your ‘hands’ of my network config thank you)

I fired it up for you … Powered down 12 Watt which is just the PSU and the IMM (I had one power supply connected) Then when powered up 100 Watt

The IMM info, one PSU with 230 Volt feed:

Bear in mind I had no VM’s running…

I have an x3500m4 but found it using way too much energy for my requirements. A regular pc does the job for less than 25% of the electricity.

So, i’d say check your needs and the footprint. Electricity bill comes every month and something runnin 24/7 adds up real quick.

It does not. It does not uses ports at all. Fail2ban monitors your logfiles and activates the firewall to block IP’s that matched your rules.

t.ex. You can block an IP that tried to access https://<url>/admin. You can block an IP that used wrong credentials x times to login on an ssh port. Or block one that tried to relay via your mailserver. The duration is configurable and alternative duration can be configured for recidivists.

And yes, you can whitelist IP’s to avoid locking yourself out. The possibilities are endless.

My usual additions:

1. Have the router to block portscanners
2. fail2ban on internet facing services.