What Is MikroTik? RouterOS and ISP Networking Explained
A practical explanation of RouterOS, MikroTik hardware, and the building blocks used by ISP and WISP operators.
RouterOS, RouterBOARD, and CHR
RouterOS provides the features operators configure: routing, VLANs, DHCP, NAT, firewall, PPPoE, Hotspot, RADIUS, queues, VPNs, and monitoring. RouterBOARD refers to MikroTik hardware platforms. CHR is the cloud-hosted RouterOS edition used on virtual machines. This distinction matters because the same menu can behave differently when CPU, interfaces, storage, or license limits differ.
Why ISPs use MikroTik
Small ISPs and WISPs often need one platform that can terminate PPPoE sessions, ask RADIUS for subscriber policy, apply queues, separate customers with VLANs, perform NAT, and expose only the management services that are needed. MikroTik is popular because those functions are available in one system and can be inspected from the CLI.
| Need | RouterOS building block | What to verify |
|---|---|---|
| Subscriber login | PPPoE + PPP profiles | Discovery interface, MTU/MRU, pool, accounting |
| Central policy | RADIUS | Source IP, UDP 1812/1813, shared secret, NAS client |
| Traffic control | Simple Queue, Queue Tree, PCQ | Direction, target, parent, marks, counters |
| Segmentation | Bridge VLAN filtering | Tagged/untagged ports and management path |
| Security | Filter, NAT, service access | Rule order, established state, restricted management |
A practical learning path
- Plan IPv4/IPv6 addressing before making interfaces.
- Build one Layer 2 segment and verify VLAN membership.
- Configure PPPoE and test a single account before adding RADIUS.
- Add RADIUS accounting and confirm Start, Interim, and Stop records.
- Add queues only after you can explain packet direction and counters.
- Harden management access and document a rollback procedure.
What MikroTik is not
It is not a magic replacement for capacity planning, radio design, upstream routing, or monitoring. A generated script can be syntactically valid while still being wrong for your topology. Use the calculators on this site to make assumptions visible, then verify them on the router.
Start with the connected toolkit
Sources and safe-use notes
This page follows the RouterOS documentation and the networking standards linked below. RouterOS syntax, hardware limits, and packet direction depend on your exact release and topology. Export a backup, test one controlled case, and keep a rollback path before applying generated output.
MikroTik documentation · RouterOS manual · RFC 4632 — CIDR · RFC 6598 — shared address space · RFC 8200 — IPv6