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

fix typo

master
sebres 2017-08-22 13:19:56 +02:00
parent 742036e9bf
commit 3d781cc379
5 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Home.md

@ -17,7 +17,7 @@
- [Fail2ban does not ban and logs include iptables v...: unknown option "-w"](How-fail2ban-works)
* #### Configuration
- [Proper fail2ban configuration](Properly-fail2ban-configuration)
- [Proper fail2ban configuration](Proper-fail2ban-configuration)
- [Fail2ban Troubleshooting](Troubleshooting)
- [How fail2ban substitution resp. runtime interpolation works](How-fail2ban-substitution-resp.-runtime-interpolation-works)
---

4
How-fail2ban-works.md

@ -3,14 +3,14 @@ But you can write resp. configure your own action to [ban something other as hos
Fail2Ban comes out-of-the-box ready to read many standard log files, such as those for sshd and Apache, and is easy to configure to read any log file you choose, for any error you choose.
**But fail2ban is just a tool, so it should be [properly configured](Properly-fail2ban-configuration).**
**But fail2ban is just a tool, so it should be [properly configured](Proper-fail2ban-configuration).**
***
**[Q]** Fail2ban does not detect some authentication failures resp. banning does not occurred
<details><summary>Answer</summary>
**[A]** There can be many reasons:
- corresponding jail for scanning the log file or systemd journal is not enabled (or idle). See [here](Properly-fail2ban-configuration) how the jail can be enabled.
- corresponding jail for scanning the log file or systemd journal is not enabled (or idle). See [here](Proper-fail2ban-configuration) how the jail can be enabled.
- the proper path to the log files (parameter `logpath`) resp. proper journal control parameter `journalmatch` should be set for this jail.
- the IP goes to ban if it makes at least `maxretry` failures within `findtime` seconds. So if you've configured `maxretry=5` and `findtime=10m` (default values) then it needs at least 5 failures (5 attempts) within 10 minutes to ban an IP.<br/>
Each failure (attempt) will be logged in `fail2ban.log` as:<br/>

0
Properly-fail2ban-configuration.md → Proper-fail2ban-configuration.md

2
Troubleshooting.md

@ -1,4 +1,4 @@
Please read [proper fail2ban configuration](Properly-fail2ban-configuration) carefully before and follow the instructions there.<br/>
Please read [proper fail2ban configuration](Proper-fail2ban-configuration) carefully before and follow the instructions there.<br/>
Many issues are configuration-related and can be relative easy rectified by the adjustment of the configuration.
***

2
_Sidebar.md

@ -6,6 +6,6 @@
---
### FAQ
* #### Configuration
- [Proper fail2ban configuration](Properly-fail2ban-configuration)
- [Proper fail2ban configuration](Proper-fail2ban-configuration)
- [Fail2ban Troubleshooting](Troubleshooting)
- [How fail2ban substitution resp. runtime interpolation works](How-fail2ban-substitution-resp.-runtime-interpolation-works)