style 💎: Fix table formatting and add code block for list_banned task
All checks were successful
ansible-lint / Ansible Lint (push) Successful in 13s
Gitleaks Scan / gitleaks (push) Successful in 5s
Markdown Lint / markdown-lint (push) Successful in 5s
ai-reviews / Review PR (pull_request) Successful in 37s
PR check / Gitleaks (pull_request) Successful in 5s
PR check / lint tests (pull_request) Successful in 15s
PR check / labeler (pull_request) Successful in 2s
PR check / handle_failures (pull_request) Has been skipped
PR check / handle_success (pull_request) Successful in 1s
All checks were successful
ansible-lint / Ansible Lint (push) Successful in 13s
Gitleaks Scan / gitleaks (push) Successful in 5s
Markdown Lint / markdown-lint (push) Successful in 5s
ai-reviews / Review PR (pull_request) Successful in 37s
PR check / Gitleaks (pull_request) Successful in 5s
PR check / lint tests (pull_request) Successful in 15s
PR check / labeler (pull_request) Successful in 2s
PR check / handle_failures (pull_request) Has been skipped
PR check / handle_success (pull_request) Successful in 1s
This commit addresses the formatting issues in the table and adds a code block for the 'list_banned' task to improve readability and clarity.
This commit is contained in:
@@ -38,19 +38,19 @@ IP banning. It supports both single-node and clustered Proxmox setups.
|
|||||||
The playbook uses the following variables (can be defined in a `vars` file or
|
The playbook uses the following variables (can be defined in a `vars` file or
|
||||||
inventory group vars):
|
inventory group vars):
|
||||||
|
|
||||||
| Variable | Description | Default |
|
| Variable | Description | Default |
|
||||||
|--------------------------|-------------------------------------|------------------|
|
|-------------------------|---------------------------------|-----------------|
|
||||||
| `f2b_bantime` | Ban per tentativi falliti | `600s` |
|
| `f2b_bantime` | Ban per tentativi falliti | `600s` |
|
||||||
| `f2b_findtime` | Finestra per contare i fallimenti | `1200s` |
|
| `f2b_findtime` | Finestra per contare fallimenti | `1200s` |
|
||||||
| `f2b_maxretry` | Tentativi prima del ban | `5` |
|
| `f2b_maxretry` | Tentativi prima del ban | `5` |
|
||||||
| `f2b_bantime_increment` | Abilita ban incrementale | `true` |
|
| `f2b_bantime_increment` | Abilita ban incrementale | `true` |
|
||||||
| `f2b_bantime_factor` | Fattore aumento ban | `2` |
|
| `f2b_bantime_factor` | Fattore aumento ban | `2` |
|
||||||
| `f2b_bantime_max` | Durata massima del ban | `7d` |
|
| `f2b_bantime_max` | Durata massima del ban | `7d` |
|
||||||
| `f2b_recidive_bantime` | Ban per recidiva | `3600` |
|
| `f2b_recidive_bantime` | Ban per recidiva | `3600` |
|
||||||
| `f2b_recidive_findtime` | Finestra recidiva | `86400` |
|
| `f2b_recidive_findtime` | Finestra recidiva | `86400` |
|
||||||
| `f2b_recidive_maxretry` | Tentativi recidiva | `3` |
|
| `f2b_recidive_maxretry` | Tentativi recidiva | `3` |
|
||||||
| `f2b_ipset_name` | Nome IPSet per IP bannati | `f2b-blacklist` |
|
| `f2b_ipset_name` | Nome IPSet per IP bannati | `f2b-blacklist` |
|
||||||
| `f2b_unban_ip` | IP da sbloccare | `""` |
|
| `f2b_unban_ip` | IP da sbloccare | `""` |
|
||||||
|
|
||||||
> All `clustered` and `pmxcfs_running` checks default to `false` to prevent
|
> All `clustered` and `pmxcfs_running` checks default to `false` to prevent
|
||||||
> errors on non-clustered or single-node setups.
|
> errors on non-clustered or single-node setups.
|
||||||
@@ -68,7 +68,11 @@ ansible-playbook -i inventory fail2ban-proxmox.yml
|
|||||||
### 2. List current banned IPs
|
### 2. List current banned IPs
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
ansible-playbook -i inventory fail2ban-proxmox.yml -e "f2b_ipset_name=fail2ban" -t list_banned
|
ansible-playbook \
|
||||||
|
-i inventory \
|
||||||
|
fail2ban-proxmox.yml \
|
||||||
|
-e "f2b_ipset_name=fail2ban" \
|
||||||
|
-t list_banned
|
||||||
```
|
```
|
||||||
|
|
||||||
### 3. Unban a specific IP
|
### 3. Unban a specific IP
|
||||||
|
|||||||
Reference in New Issue
Block a user