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

Formatting on Error iptables changed and small fixes

master
pixel::doc 2025-01-10 00:03:44 +01:00
parent d2cdb0a196
commit 6fb1f125eb
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
Fail2Ban-and-Docker.md

@ -42,11 +42,12 @@ Now you are directly protecting the services in which the attack is occurring, r
# Error: "iptables: No chain/target/match by that name" with Docker Host using iptables-legacy
Check if the Docker Container and the Docker Host are using the same iptables Version. Run `iptables --version` on the Docker Host and in the Docker Container.
If the Docker Host is using iptables-legacy, than you need to change the banaction in your fail2ban.local
If the Docker Host is using iptables-legacy, than you need to change the `banaction` in your `fail2ban.local`:
```ini
[DEFAULT]
banaction = iptables-multiport[iptables=iptables-legacy]
```
NOTE: UNRAID 6.12.14 as Docker Host is using `iptables v1.8.9 (legacy)` and the fail2ban 1.1.0 docker contain is using `iptables v1.8.10 (nf_tables)`.
NOTE: UNRAID 6.12.14 as Docker Host is using `iptables v1.8.9 (legacy)` and the fail2ban 1.1.0 docker container is using `iptables v1.8.10 (nf_tables)` by default.