Port details on branch 2023Q4 |
- crowdsec-firewall-bouncer CrowdSec bouncer written in golang for firewalls
- 0.0.27_3 security
=0 0.0.27_3Version of this port present on the latest quarterly branch. - Maintainer: marco@crowdsec.net
 - Port Added: 2023-12-07 15:09:06
- Last Update: 2023-12-07 15:06:56
- Commit Hash: 1a5ede5
- License: MIT
- WWW:
- https://github.com/crowdsecurity/cs-firewall-bouncer
- 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.
¦ ¦ ¦ ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - Dependency lines:
-
- crowdsec-firewall-bouncer>0:security/crowdsec-firewall-bouncer
- To install the port:
- cd /usr/ports/security/crowdsec-firewall-bouncer/ && make install clean
- To add the package, run one of these commands:
- pkg install security/crowdsec-firewall-bouncer
- pkg install crowdsec-firewall-bouncer
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.- PKGNAME: crowdsec-firewall-bouncer
- Flavors: there is no flavor information for this port.
- distinfo:
- TIMESTAMP = 1684281311
SHA256 (crowdsecurity-cs-firewall-bouncer-v0.0.27-freebsd_GH0.tar.gz) = 1dba0604d0ff7d9035e2e2adcff42cddf7d0b63f23dd973ce692b6e18ee65126
SIZE (crowdsecurity-cs-firewall-bouncer-v0.0.27-freebsd_GH0.tar.gz) = 2600838
Packages (timestamps in pop-ups are UTC):
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- git : devel/git@lite
- gmake>=4.3 : devel/gmake
- go120 : lang/go120
- There are no ports dependent upon this port
Configuration Options:
- No options to configure
- Options name:
- security_crowdsec-firewall-bouncer
- USES:
- gmake go:no_targets
- pkg-message:
- For install:
-
crowdsec-firewall-bouncer is installed.
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 another 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:
----------
# sysrc pf_enable=YES
pf_enable: NO -> YES
# service pf start
Enabling pf.
----------
Add the following in /etc/pf.conf to create the firewall tables and rules:
----------
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
----------
To apply the file:
# pfctl -f /etc/pf.conf
Then activate the bouncer via sysrc and run it:
----------
# sysrc crowdsec_firewall_enable="YES"
crowdsec_firewall_enable: NO -> YES
# service crowdsec_firewall start
----------
- Master Sites:
|
Number of commits found: 1
Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
Commit | Credits | Log message |
0.0.27_3 07 Dec 2023 15:06:56
    |
Ashish SHUKLA (ashish)  |
all: Bump PORTREVISION after lang/go* update
PR: 274405
(cherry picked from commit 0505b712df3ae2b4bcaba00aecc7c1e9100d8609) |
Number of commits found: 1
|