Skip to content

enhance: add new iptables opts #841

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 4, 2025
Merged

enhance: add new iptables opts #841

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 27 additions & 1 deletion crowdsec-docs/unversioned/bouncers/firewall.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -342,6 +342,11 @@ Skip verification of the API certificate, typical for self-signed certificates

disable interacting with ipv6 chains/sets, defaults to `false`

### `disable_ipv4`
> `true` | `false`

disable interacting with ipv4 chains/sets, defaults to `false`

### `deny_action`
> `DROP` | `REJECT`

Expand All @@ -362,7 +367,7 @@ if logging is true, this sets the log prefix, defaults to "crowdsec: "
### `iptables_chains`
> []string

specify a list of chains to insert rules
specify a list of chains to insert rules into both ipv4 and ipv6

```yaml
iptables_chains:
Expand All @@ -375,6 +380,27 @@ iptables_chains:
If you are using a dockerized application and allow remote connections to the exposed port, you need to add the `DOCKER-USER` chain to the list of chains.
:::

### `iptables_v4_chains`
> []string

Specify a list of chains to insert rules into ipv4 only

```yaml
iptables_v4_chains:
- INPUT
- DOCKER-USER
```

### `iptables_v6_chains`
> []string

Specify a list of chains to insert rules into ipv6 only

```yaml
iptables_v6_chains:
- INPUT
```

### `blacklists_ipv4`
> string

Expand Down