BSD Portssecurity/crowdsec-firewall-bouncer 0.0.31_1 DragonFly
CrowdSec bouncer written in golang for firewalls
- System
- DragonFly
- Repository
- DPorts
- Maintainer
- [email protected] (as in FreeBSD)
- License
- MIT
- Categories
- security
- Package size
- 3764.9 KiB, 12760.4 KiB installed
Description
Crowdsec bouncer written in golang for firewalls.
cs-firewall-bouncer will fetch new and old decisions from a CrowdSec API to add them in a blocklist used by supported firewalls.
In the other systems
The newest version among them is 0.0.38, as upstream numbers it.
| System | Port | Version | Vulnerabilities | Status | Maintainer | Last update |
|---|---|---|---|---|---|---|
| DragonFly | security/crowdsec-firewall-bouncer | 0.0.31_1 behind since 2026-09-15 | none known | - | [email protected] | - |
| FreeBSD | security/crowdsec-firewall-bouncer | 0.0.38_2 newest | none known | - | [email protected] | 2026-10-20 |
| OpenBSD | security/crowdsec-firewall-bouncer | 0.0.34 behind since 2026-09-15 | no data | - | Robert Nagy <[email protected]> | - |
| MidnightBSD | security/crowdsec-firewall-bouncer | 0.0.28_10 behind since 2026-09-15 | no data | - | [email protected] | - |
| HardenedBSD | security/crowdsec-firewall-bouncer | 0.0.38 newest | no data | - | [email protected] | - |
| GhostBSD | security/crowdsec-firewall-bouncer | 0.0.36 behind since 2026-09-30 | no data | - | [email protected] | - |
| OPNsense | security/crowdsec-firewall-bouncer | 0.0.34_3 behind since 2026-09-15 | no data | - | [email protected] | - |
Install
Binary package:
pkg install crowdsec-firewall-bouncerFrom DPorts:
cd /usr/dports/security/crowdsec-firewall-bouncer && make install cleanDependencies
No port depends on this one.
Configuration
No options to configure.
- Service scripts
- none
Message after installing
crowdsec-firewall-bouncer is installed. Note: If you are using OPNsense or pfSense, ignore the following instructions and use the settings page of the CrowdSec plugin. ----- If you are running crowdsec on this machine, the bouncer will register itself with the Local API when it's started the first time. If the LAPI is on a different machine, you need to manually register the bouncer and fill api_key and api_url in /usr/local/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml before starting the service. This package depends on the Packet Filter service. To make sure it's active: ---------- # service pf enable pf enabled in /etc/rc.conf # service pf start Enabling pf. ---------- Add the following in /etc/pf.conf to create the firewall tables and rules. If the start command complained about missing pf.conf, you'll have to run it again. ---------- table <crowdsec-blacklists> persist table <crowdsec6-blacklists> persist block drop in quick from <crowdsec-blacklists> to any block drop in quick from <crowdsec6-blacklists> to any ---------- If you already have any pass rule, you may want to put the block rules before them. To apply the file: # pfctl -f /etc/pf.conf Then activate the bouncer service and run it: ---------- # service crowdsec_firewall enable crowdsec_firewall enabled in /etc/rc.conf # service crowdsec_firewall start ----------