Skip to content

cs-mikrotik-bouncer-alt

Requirements

cs-mikrotik-bouncer-alt

General Info
General Info
- About
- Features
- Known Limitations
- Comparison
- To Do
Configuration
Configuration
- Requirements Requirements
  Table of contents
  - Prerequisites
  - Configuration and deployment overview
- Mikrotik config
- Bouncer config
Deployment
Deployment
Development

Overview

For now, this service is mainly thought to be used in as an app in a container.

If you need to build from source and run as standalone binary, please see deployment section.

The app alone takes about up to 60MB or memory (depends on how large blocklists are). CPU usage is minimal, 10 milicores should be enough.

Please see also Known Limitations.

Prerequisites

You should have a MikroTik appliance and a CrowdSec instance running.
The bouncer container is available as docker image under quay.io/kaszpir/cs-mikrotik-bouncer-alt.
The running container must have access to CrowdSec LAPI and to MikroTik RouterOS API.

Configuration and deployment overview

Read the following instructions below doing anything.

Configure MikroTik device by adding user and firewall rules.
Create a bouncer in CrowdSec.
Prepare config for the bouncer
Start the bouncer app via standalone binary or a container.
Verify if all works as expected.