MikroTik Manager documentation¶
Reference material for people already running the platform. If you are still deciding whether to try it, the project README is the better starting point.
| Document | Covers |
|---|---|
| Configuration | Environment variables, secret management and key rotation |
| Devices | The device list, the tabs on a device, ports and VLANs, and the per-device tools |
| Clients | Where client data comes from, identification, history, and per-port clients |
| Topology | How links are discovered, spanning-tree resolution, client devices, your own nodes and hand-drawn links |
| Traffic analytics | The NetFlow collector, top talkers, application breakdown, retention |
| Wireless | Radios and SSIDs, RF health, signal bands, rogue APs, guest WiFi |
| Network services | DHCP, DNS, NTP, WireGuard, logging, discovery and SNMP |
| Adopting devices | Adding configured devices, and configuring factory-default ones so they can be managed |
| Sites | Grouping devices into sites, switching between them, and what each site scopes |
| Change Guard and Config Health | How the safety system works, its settings, and what to expect when it fires |
| Security page | Firewall posture, certificates, and known vulnerabilities (CVEs) in the fleet's RouterOS versions |
| Alerting | Alert rules, delivery channels, webhooks, scheduled reports, maintenance windows |
| Single sign-on (OIDC) | Identity provider setup, group-to-role mapping, break-glass behaviour |
| CAPsMAN | How centrally provisioned access points are modelled, and current limits |
| User Manager | RouterOS's RADIUS server: sessions, users, groups and their attributes, and clearing a stuck session |
| Cellular (LTE) | Signal, carriers, tower movement, and the data-cap reset SMS |
| SSH keys | Per-device keypairs, rotation, and what installing one costs |
| Bulk commands | Running one command across a fleet, in waves |
| Firmware rollouts | Waves, the upgrade pipeline, and what upgrading several at once costs |
| Backups | Finding, reading, comparing and deleting configuration backups |
| Polling and scaling | Poller health, headroom, tuning, and clearing a backlog |
| API and automation | Scoped tokens, authentication, and driving the platform from scripts |
| Architecture | How the system is put together, for contributors |
Conventions used here¶
- Settings in the UI are stored in the database and apply without a restart.
- Environment variables live in
.envand require a container restart to change. - Anything described as read-only makes no writes to your devices.
Which version is this?¶
These pages describe a specific release, shown in the header. The platform ships frequently, so if something here does not match what you see, check that the version you are running matches the version you are reading.