docs: clarify centralized ban lifetime

README.md

@@ -34,7 +34,9 @@ logpath = %(sshd_log)s
 backend = %(sshd_backend)s
 maxretry = 3
 findtime = 1200
-bantime  = 5
+# This is only Fail2Ban's local cooldown. The gateway [AutoUnban] policy
+# determines the actual centralized ban duration.
+bantime  = 1
 ```
 
 Важно: в графе action выставлять значение eterban. Желательно в name указывать причину блокировки.

prod-server/etc/fail2ban/action.d/eterban.conf

 [Definition]
-actionban = /usr/share/eterban/ban.py <ip> <name>
\ No newline at end of file
+# The gateway owns unban timing through AutoUnban. An actionunban command here
+# would prematurely remove the central ban when Fail2Ban's local bantime ends.
+actionban = /usr/share/eterban/ban.py <ip> <name>

prod-server/etc/fail2ban/jail.d/jail.conf

@@ -22,7 +22,10 @@
 # defined using space separator.
 ignoreip = 127.0.0.1/8 87.249.47.42/29 89.104.102.10/28 212.176.200.18/28 62.16.105.243/28 10.20.30.10/24 91.232.225.0/24
 
-# "bantime" is the number of seconds that a host is banned.
+# Eterban publishes the ban to the gateway; the gateway AutoUnban policy owns
+# the actual ban lifetime. Keep this short only to release Fail2Ban's local
+# state after actionban has run. Do not add actionunban for the eterban action.
+# "bantime" is the number of seconds that a host is banned locally by Fail2Ban.
 #bantime  = 600
 bantime   = 1
 # A host is banned if it has generated "maxretry" during the last "findtime"