CrowdSec Mikrotik Bouncer

CrowdSec Mikrotik Bouncer is a CrowdSec bouncer for self-hosters running MikroTik RouterOS that blocks malicious IP addresses by populating a dynamic firewall…

  • Security
CrowdSec Mikrotik Bouncer is a CrowdSec bouncer for self-hosters running MikroTik RouterOS that blocks malicious IP addresses by populating a dynamic firewall address list through the MikroTik API; the upstream repository is archived and the maintained fork, cs-mikrotik-bouncer-alt, is available.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

37/100 Low

Maintained
0GitHub repository is archived
Popular
3767 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
95512 MB minimum RAM, runs on ARM
Security check
72no serious findings, 3 minor, CI

Availability: platform listings confirmed today, links checked 27 days ago

GitHub stars
67
Open issues
4
Last commit
2025-06-08
Latest release
v0.7.3
License
Apache-2.0
Activity
stale

Checked 21 days ago - source: GitHub (funkolab/cs-mikrotik-bouncer)

Resources & Compatibility

Minimum requirements: 512 MB RAM. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Fill in your CrowdSec tokens first Replace <TOKEN1> and <TOKEN2> with your CrowdSec API tokens (secret codes that let the bouncer talk to CrowdSec). If you leave the placeholder words in, the bouncer won't be able to connect or block properly. source
  • Edit the YAML config before starting After generating it, open the YAML (a plain-text settings file) in /etc/crowdsec/bouncers/ and check the values. Without the right settings, the service may start but not enforce the blocks you expect. source
  • Run it as a background service Start it with the systemctl (the Linux service manager) command so it keeps running after you close the terminal, or use the -S command if you want to run it directly. If neither is run, the bouncer is installed but not actively blocking. source
  • Maintenance status The original repository is no longer actively maintained; the author recommends the community fork cs-mikrotik-bouncer-alt for ongoing use. source
  • Alternative maintained bouncer This repository is no longer actively maintained; use nvtkaszpir/cs-mikrotik-bouncer-alt. source
  • Maintained alternative The archived README points to nvtkaszpir/cs-mikrotik-bouncer-alt as the maintained alternative. source

Fetched 5 days ago - each note links to its source

Alternatives (3)

  • Fail2ban - Fail2ban is a daemon that monitors log files and automatically bans hosts that cause multiple authentication failures, using firewall rules…
  • IPBanPro - IPBan is a FREE and open source application that allows auto banning ip addresses from failed login attempts.
  • defensia-agent

Checked 41 days ago - source: AlternativeTo

Common questions

How do I generate the API key for this MikroTik bouncer?

Run cscli bouncers add mikrotik-bouncer and copy the key that is printed immediately. Set that value as CROWDSEC_BOUNCER_API_KEY because the key will not be shown again.

What network access does the bouncer container need?

The container must be able to reach both the CrowdSec instance and the MikroTik appliance.

How do CrowdSec decisions become router firewall blocks?

The bouncer uses the MikroTik API to populate a dynamic firewall address list. You then create IP drop filter rules in the MikroTik firewall.

How should the bouncer be deployed?

It is primarily intended to run as a Docker container. If building from source, the repository's Dockerfile can be used as a reference.

Answers sourced from app.crowdsec.net

Community

Collected 49 days ago - public community threads