github
/
fail2ban
mirror of https://github.com/fail2ban/fail2ban
1
0
Fork 0
Code Issues Releases Wiki Activity

Added Q on why empty chains are not created directly on startup

master
zb226 2024-10-26 14:17:28 +02:00
parent 62a97244c7
commit 7bd2c3572f
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
How-fail2ban-works.md

@ -123,3 +123,9 @@ Following script shows all failures of all IPs across all jails:
lockingopt =
```
</details>
***
**[Q]** After Fail2ban starts, I'm not seeing the filter chains I expect as per my configuration
<details><summary>Answer</summary>
**[A]** Fail2ban will create the filter chains on demand, i.e. as the first bans actually happen. This behaviour was changed in fail2ban 0.10 - prior to that version empty chains were created directly at startup (see also [this SO answer](https://stackoverflow.com/a/68622588/1529709) and [#1742](https://github.com/fail2ban/fail2ban/pull/1742)).