Also had to fiddle with the firewall again because its only set to a IP limit of a million IP addresses for the blacklist. Then Fail2ban started churning out errors because it could not add more IPs to the blacklist because it was basically full
So now I have increased the blacklist size to 5 million IP's. Because its getting rather ridiculous about the amount of IPs which are being banned individually, GPT5 is writing a script for me which will scan the blacklist and find clusters of IP addresses within a similar range, it will just outright ban the range in a second blacklist and then remove the original individual IP is from the original blacklist. This will basically stop the blacklist from getting stupidly large.
I didn't want to start blocking entire ranges like this, but it has become a necessity at this point. I'm only blocking the /24 range at the moment but I may have to tighten up on that at a later date as well. Of course the higher the range I ban, the more chance there will be of collateral damage I think..
. So the problem is when it is restarted, it then restores bans from its own database which can literally be millions of IPs. There is actually no point in doing that in my setup because I am just permanently banning IPs anyway now.
