rhino/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-03-26 03:39:20 -07:00
Code Issues Packages Projects Releases Wiki Activity

Add Note for Synology DSM Docker Users

yolylight
2024-10-13 21:41:12 +08:00
parent 4f8faa57b8
commit ae0a213e40
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
Fail2Ban-Setup.md

@@ -161,6 +161,14 @@ Docker uses the `FORWARD` chain instead of the default INPUT chain. If the machi
chain = FORWARD chain = FORWARD
``` ```
###### Note for Synology DSM Docker Users
Please set the `chain` to `DOCKER-USER`
```ini
chain = DOCKER-USER
```
###### Note for Docker Users with Fail2Ban v1.1.1.dev1 (and possibly newer) ###### Note for Docker Users with Fail2Ban v1.1.1.dev1 (and possibly newer)
With Fail2Ban v1.1.1.dev1 the default `banactions` for Debian changed from iptables to nftables (see [here](https://github.com/fail2ban/fail2ban/commit/d0d07285234871bad3dc0c359d0ec03365b6dddc)). Docker (at least version 25.0.3) on the other hand still uses iptables. Hence, the requests to the Docker containers are not blocked with `banaction = %(banaction_allports)s`. In this scenario, use With Fail2Ban v1.1.1.dev1 the default `banactions` for Debian changed from iptables to nftables (see [here](https://github.com/fail2ban/fail2ban/commit/d0d07285234871bad3dc0c359d0ec03365b6dddc)). Docker (at least version 25.0.3) on the other hand still uses iptables. Hence, the requests to the Docker containers are not blocked with `banaction = %(banaction_allports)s`. In this scenario, use