Merge branch 'main' into cve-explorer-docs

Author: buixor

crowdsec-docs/blog/2024-06-11-cscli_dashboard_deprecation.md

@@ -19,9 +19,13 @@ Some users using `cscli dashboard` command did not understand what was happening
 
 ## What will happen to the `cscli dashboard` command ?
 
-The `cscli dashboard` command will be deprecated in version `1.7.0` of the CrowdSec package. However, we don't want to leave users without a solution to visualize their data. We are working on a new way to deploy the Metabase dashboard via a script that will automate the deployment of the dashboard.
+The `cscli dashboard` command will be deprecated starting from version `1.7.0` of the CrowdSec package. Moving forward, users will have the following alternatives for viewing metrics and insights:
 
-A development version of the script can be found linked [here](https://github.com/crowdsecurity/crowdsec/issues/2927)
+* CrowdSec Console (officially supported)
+* Prometheus with Grafana
+* VictoriaMetrics with Grafana
+
+Please note that **only the CrowdSec Console is officially supported by the CrowdSec team**. The other options are provided for flexibility but are community-driven and require self-management.
 
 ## What should I do now?
 
@@ -31,4 +35,6 @@ Currently we recommend that you firstly check which version of Metabase that is
 docker ps -a
 ```
 
-This will show you the running containers on your system. Look for the Metabase container and check the version of the container. If you are running a version of Metabase that is vulnerable to a CVE, we recommend that you update to latest version of CrowdSec then re run the `cscli dashboard` command to update the Metabase dashboard.
+This will show you the running containers on your system. Look for the Metabase container and check its version. If you are running a version of Metabase that is vulnerable to a CVE, we recommend updating to the latest version of CrowdSec and re-running the `cscli dashboard` command to refresh the Metabase dashboard.
+
+**If you are already on version `1.7.0`, you will need to manually remove the container, as the `cscli dashboard` command is no longer available.**

crowdsec-docs/unversioned/bouncers/firewall.mdx

@@ -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`
 
@@ -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:
@@ -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
 

crowdsec-docs/unversioned/getting_started/post_installation/whitelists.mdx

@@ -13,7 +13,7 @@ By default CrowdSec will whitelist private LAN IP addresses via [this parser](ht
 
 In this guide we will cover how to create some whitelists and how to apply them to your CrowdSec instance.
 
-However, we can't cover every possible use case, so if you have a specific one that isn't covered here, please refer to [detailed whitelist documentation](/docs/next/whitelist/intro)
+However, we can't cover every possible use case, so if you have a specific one that isn't covered here, please refer to [detailed whitelist documentation](/docs/next/log_processor/whitelist/intro)
 
 :::info
 We use "event" as a term to describe a log line that is currently being processed by CrowdSec. An "event" can be a log line from a log file, or an "overflow" from a scenario.