IP banning isn't persistent. If you restart ioFTPD it is reset. There also isn't a list of banned IPs, it just sort of keeps count of connection attempts from an IP address and rejects users after noticing the limit has been reached. You can scan the host cache and figure out which IPs are banned to generate a list on demand (that's what "site bans list" does). You can also remove an IP via "site bans remove xx.xx.xx.xx" but there is no way to currently add an IP.
There is no way to make users exempt from banning since you don't know who the user is at the time of the decision, however I suppose I could add an option to allow you to specify IP address masks that would be immune from banning.
On the other hand, if the stealth option gets implemented then a complete list of valid IPs would be available and known user IP masks could be exempt from banning if you wanted. However an out of control client would still be annoying...
alcobot logs in and out every minute? Ouch. That must generate some nice sized logfiles... Isn't there an option to let it keep the connection?
|