RouterOS Fundamentals
RouterOS Is NOT GNU/Linux
RouterOS runs a Linux kernel (5.6.3) but everything above the kernel is MikroTik's proprietary nova system. This is the single most important fact for agents to internalize.
What does NOT exist on RouterOS:
- No
/bin, /usr, /etc, /var — no FHS layout
- No bash, sh, ash, zsh — no Unix shell at all
- No coreutils (
ls, cat, grep, ps, mount, ip, iptables, etc.)
- No glibc, musl, busybox
- No apt, pkg, opkg — no package manager (packages are
.npk files installed via upload + reboot)
- No
systemctl, service, init system
- No
/proc or /sys accessible from userland
- No
docker, podman — RouterOS has its own /container subsystem (7.x+)
What DOES exist:
- RouterOS CLI — its own language, not shell. Accessed via SSH, serial, WinBox, or WebFig
- REST API at
/rest/ (HTTP, port 80 by default) — the primary programmatic interface
- RouterOS scripting language (
.rsc files) — its own syntax, not bash. See the routeros-scripting skill and Scripting reference
- WebFig (web UI) on port 80
- WinBox protocol on port 8291
Common agent mistakes to avoid:
- Do NOT try
ssh admin@host 'ls /' — it opens RouterOS CLI, not a shell
- Do NOT suggest
mount, fdisk, mkfs — use /disk commands instead
- Do NOT look for config files at
/etc/ — configuration is in the RouterOS database
- Do NOT assume
ping works the same — it's /tool/ping or /ping in CLI
- Do NOT suggest installing packages via
apt or opkg — upload .npk via SCP then /system/package/apply-changes (7.18+) or /system/reboot (<7.18)
- See Extra packages reference for the full package list and installation pattern
RouterOS CLI Syntax
RouterOS CLI uses path-based navigation, not Unix command pipelines:
# Navigation
/ip/address/print
/interface/print
/system/resource/print
# Adding entries
/ip/address/add address=192.168.1.1/24 interface=ether1
# Modifying (by internal ID or find expression)
/ip/address/set [find interface=ether1] address=10.0.0.1/24
# Removing
/ip/address/remove [find address="192.168.1.1/24"]
# Running a command
/system/reboot
/tool/fetch url="http://example.com/file.npk" dst-path="/"
Key syntax differences from shell:
= assigns properties (no spaces around it)
[find ...] is the query expression (like WHERE)
- Interactive
print row numbers are not script-safe object IDs; use [find ...] or *HEX internal IDs
- Strings use
"" (double quotes only)
- Comments use
#
- Variables:
:local myVar "value" and $myVar
- No pipes, no redirection, no subshell
REST API
RouterOS REST API at http://HOST:PORT/rest/. HTTP verbs map non-standardly:
| HTTP |
RouterOS Action |
CLI Equiv |
GET |
print (list/read) |
/path/print |
PUT |
add (create) |
/path/add |
PATCH |
set (update) |
/path/set |
DELETE |
remove |
/path/remove |
POST |
command (execute) |
/path/command |
Key gotchas:
PUT creates (NOT updates) — opposite of many REST APIs
- Empty password auth:
admin: (colon required, nothing after)
- WebFig root (
GET /) returns HTTP 200 without auth — use as health check
- REST API (
/rest/) requires auth (HTTP 401 without it)
.id field is *HEX format (e.g., *1, *A)
See REST API reference for full patterns, error handling, filtering, POST commands, and /console/inspect.
Version Scheme
Format: MAJOR.MINOR[.PATCH][betaN|rcN] — e.g., 7.22, 7.22.1, 7.23beta2, 7.22rc1
Channels: stable / long-term / testing / development
Version endpoint (plain text): https://upgrade.mikrotik.com/routeros/NEWESTa7.<channel>
For version parsing, comparison, download URLs, and package naming: see Version parsing reference.
Architecture Names
MikroTik uses these architecture identifiers (not standard Linux arch names):
| MikroTik name |
CPU |
Common hardware |
x86 |
x86_64 |
CHR, x86-based RouterBOARDs |
arm64 |
aarch64 |
Modern ARM boards (RB5009, Chateau) |
arm |
ARMv7 |
Older ARM boards |
mipsbe |
MIPS big-endian |
Legacy RouterBOARDs |
mmips |
MIPS multi-core |
hAP ac, RB4011 |
smips |
MIPS single-core |
hAP lite, mAP |
ppc |
PowerPC |
CCR1xxx series |
tile |
Tilera |
CCR (older models) |
CHR (Cloud Hosted Router) is available only for x86 and arm64.
Default Credentials
- Username:
admin
- Password: (empty — no password)
- On first login via SSH/console, RouterOS 7.x prompts to set a password or press
a to skip
- REST API and WebFig allow empty-password access
Inspecting Hardware from RouterOS CLI
# PCI devices (the RouterOS equivalent of lspci)
/system/resource/hardware/print
# IRQ assignments (shows driver binding)
/system/resource/irq/print
# System overview
/system/resource/print
# Disk info
/disk/print
# Installed packages
/system/package/print
# IP services and ports
/ip/service/print
# Network interfaces
/interface/print
Additional Resources
Reference files:
- New official manual home: https://manual.mikrotik.com/. The new site is replacing older Confluence-based
help.mikrotik.com docs and includes a CLI Reference section at https://manual.mikrotik.com/docs/CLI%20Reference/.
- For REST API details and
/console/inspect command tree: see REST API reference
- For version parsing, comparison, and download URL logic: see Version parsing reference
- For extra packages (container, iot, zerotier, etc.): see Extra packages reference
- For device-mode (modes, feature matrix, physical confirmation): see Device-mode reference
- For RouterOS scripting language syntax: see Scripting reference
- For user management, SSH keys, admin account: see Users REST reference
- For IP addressing, routing, DHCP, DNS, interfaces: see Networking REST reference
- For firewall filter/NAT/mangle and rule ordering: see Firewall REST reference
- For Bun runtime bugs affecting HTTP (req.destroy, pool, secrets): see Bun runtime gotchas
Related skills:
- For RouterOS scripting and
.rsc/CLI config automation gotchas: see the routeros-scripting skill
- For the /container subsystem (VETH, device-mode, lifecycle): see the
routeros-container skill
- For netinstall-cli and device flashing: see the
routeros-netinstall skill
- For the /app YAML container format (7.22+): see the
routeros-app-yaml skill
- For /console/inspect tree traversal and schema generation: see the
routeros-command-tree skill
- For running CHR in QEMU (local or CI): see the
routeros-qemu-chr skill
- For packet capture, /tool/sniffer, and TZSP streaming: see the
routeros-sniffer skill
MCP tools:
- For command tree browsing and property lookups: use the
rosetta MCP server tools (routeros_search, routeros_get_page, routeros_command_tree)
1---
2name: routeros-fundamentals
3description: "RouterOS v7 domain knowledge for AI agents. Use when: working with MikroTik RouterOS, writing RouterOS CLI/script commands, calling RouterOS REST API, debugging why a Linux command fails on RouterOS, or when the user mentions MikroTik, RouterOS, CHR, or /ip /system /interface paths. Scope: RouterOS 7.x (long-term and newer) only — v6 is NOT covered and accuracy for v6 problems will be low."
4metadata:
5 source: https://skillmd.com/skills/tikoci/routeros-fundamentals
6---
7
8# RouterOS Fundamentals
9
10## RouterOS Is NOT GNU/Linux
11
12RouterOS runs a Linux kernel (5.6.3) but **everything above the kernel is MikroTik's proprietary `nova` system**. This is the single most important fact for agents to internalize.
13
14**What does NOT exist on RouterOS:**
15
16- No `/bin`, `/usr`, `/etc`, `/var` — no FHS layout
17- No bash, sh, ash, zsh — no Unix shell at all
18- No coreutils (`ls`, `cat`, `grep`, `ps`, `mount`, `ip`, `iptables`, etc.)
19- No glibc, musl, busybox
20- No apt, pkg, opkg — no package manager (packages are `.npk` files installed via upload + reboot)
21- No `systemctl`, `service`, init system
22- No `/proc` or `/sys` accessible from userland
23- No `docker`, `podman` — RouterOS has its own `/container` subsystem (7.x+)
24
25**What DOES exist:**
26
27- RouterOS CLI — its own language, not shell. Accessed via SSH, serial, WinBox, or WebFig
28- REST API at `/rest/` (HTTP, port 80 by default) — the primary programmatic interface
29- RouterOS scripting language (`.rsc` files) — its own syntax, not bash. See the `routeros-scripting` skill and [Scripting reference](./references/scripting.md)
30- WebFig (web UI) on port 80
31- WinBox protocol on port 8291
32
33**Common agent mistakes to avoid:**
34
35- Do NOT try `ssh admin@host 'ls /'` — it opens RouterOS CLI, not a shell
36- Do NOT suggest `mount`, `fdisk`, `mkfs` — use `/disk` commands instead
37- Do NOT look for config files at `/etc/` — configuration is in the RouterOS database
38- Do NOT assume `ping` works the same — it's `/tool/ping` or `/ping` in CLI
39- Do NOT suggest installing packages via `apt` or `opkg` — upload `.npk` via SCP then `/system/package/apply-changes` (7.18+) or `/system/reboot` (<7.18)
40- See [Extra packages reference](./references/extra-packages.md) for the full package list and installation pattern
41
42## RouterOS CLI Syntax
43
44RouterOS CLI uses path-based navigation, not Unix command pipelines:
45
46```routeros
47# Navigation
48/ip/address/print
49/interface/print
50/system/resource/print
51
52# Adding entries
53/ip/address/add address=192.168.1.1/24 interface=ether1
54
55# Modifying (by internal ID or find expression)
56/ip/address/set [find interface=ether1] address=10.0.0.1/24
57
58# Removing
59/ip/address/remove [find address="192.168.1.1/24"]
60
61# Running a command
62/system/reboot
63/tool/fetch url="http://example.com/file.npk" dst-path="/"
64```
65
66**Key syntax differences from shell:**
67
68- `=` assigns properties (no spaces around it)
69- `[find ...]` is the query expression (like WHERE)
70- Interactive `print` row numbers are not script-safe object IDs; use `[find ...]` or `*HEX` internal IDs
71- Strings use `""` (double quotes only)
72- Comments use `#`
73- Variables: `:local myVar "value"` and `$myVar`
74- No pipes, no redirection, no subshell
75
76## REST API
77
78RouterOS REST API at `http://HOST:PORT/rest/`. HTTP verbs map non-standardly:
79
80| HTTP | RouterOS Action | CLI Equiv |
81|---|---|---|
82| `GET` | print (list/read) | `/path/print` |
83| `PUT` | **add (create)** | `/path/add` |
84| `PATCH` | set (update) | `/path/set` |
85| `DELETE` | remove | `/path/remove` |
86| `POST` | command (execute) | `/path/command` |
87
88**Key gotchas:**
89
90- `PUT` creates (NOT updates) — opposite of many REST APIs
91- Empty password auth: `admin:` (colon required, nothing after)
92- WebFig root (`GET /`) returns HTTP 200 without auth — use as health check
93- REST API (`/rest/`) requires auth (HTTP 401 without it)
94- `.id` field is `*HEX` format (e.g., `*1`, `*A`)
95
96See [REST API reference](./references/rest-api-patterns.md) for full patterns, error handling, filtering, POST commands, and `/console/inspect`.
97
98## Version Scheme
99
100Format: `MAJOR.MINOR[.PATCH][betaN|rcN]` — e.g., `7.22`, `7.22.1`, `7.23beta2`, `7.22rc1`
101
102**Channels:** `stable` / `long-term` / `testing` / `development`
103
104Version endpoint (plain text): `https://upgrade.mikrotik.com/routeros/NEWESTa7.<channel>`
105
106For version parsing, comparison, download URLs, and package naming: see [Version parsing reference](./references/version-parsing.md).
107
108## Architecture Names
109
110MikroTik uses these architecture identifiers (not standard Linux arch names):
111
112| MikroTik name | CPU | Common hardware |
113|---|---|---|
114| `x86` | x86_64 | CHR, x86-based RouterBOARDs |
115| `arm64` | aarch64 | Modern ARM boards (RB5009, Chateau) |
116| `arm` | ARMv7 | Older ARM boards |
117| `mipsbe` | MIPS big-endian | Legacy RouterBOARDs |
118| `mmips` | MIPS multi-core | hAP ac, RB4011 |
119| `smips` | MIPS single-core | hAP lite, mAP |
120| `ppc` | PowerPC | CCR1xxx series |
121| `tile` | Tilera | CCR (older models) |
122
123CHR (Cloud Hosted Router) is available only for `x86` and `arm64`.
124
125## Default Credentials
126
127- Username: `admin`
128- Password: (empty — no password)
129- On first login via SSH/console, RouterOS 7.x prompts to set a password or press `a` to skip
130- REST API and WebFig allow empty-password access
131
132## Inspecting Hardware from RouterOS CLI
133
134```routeros
135# PCI devices (the RouterOS equivalent of lspci)
136/system/resource/hardware/print
137
138# IRQ assignments (shows driver binding)
139/system/resource/irq/print
140
141# System overview
142/system/resource/print
143
144# Disk info
145/disk/print
146
147# Installed packages
148/system/package/print
149
150# IP services and ports
151/ip/service/print
152
153# Network interfaces
154/interface/print
155```
156
157## Additional Resources
158
159**Reference files:**
160
161- New official manual home: <https://manual.mikrotik.com/>. The new site is replacing older Confluence-based `help.mikrotik.com` docs and includes a CLI Reference section at <https://manual.mikrotik.com/docs/CLI%20Reference/>.
162- For REST API details and `/console/inspect` command tree: see [REST API reference](./references/rest-api-patterns.md)
163- For version parsing, comparison, and download URL logic: see [Version parsing reference](./references/version-parsing.md)
164- For extra packages (container, iot, zerotier, etc.): see [Extra packages reference](./references/extra-packages.md)
165- For device-mode (modes, feature matrix, physical confirmation): see [Device-mode reference](./references/device-mode.md)
166- For RouterOS scripting language syntax: see [Scripting reference](./references/scripting.md)
167- For user management, SSH keys, admin account: see [Users REST reference](./references/routeros-users-rest.md)
168- For IP addressing, routing, DHCP, DNS, interfaces: see [Networking REST reference](./references/routeros-networking-rest.md)
169- For firewall filter/NAT/mangle and rule ordering: see [Firewall REST reference](./references/routeros-firewall-rest.md)
170- For Bun runtime bugs affecting HTTP (req.destroy, pool, secrets): see [Bun runtime gotchas](./references/bun-runtime-gotchas.md)
171
172**Related skills:**
173
174- For RouterOS scripting and `.rsc`/CLI config automation gotchas: see the `routeros-scripting` skill
175- For the /container subsystem (VETH, device-mode, lifecycle): see the `routeros-container` skill
176- For netinstall-cli and device flashing: see the `routeros-netinstall` skill
177- For the /app YAML container format (7.22+): see the `routeros-app-yaml` skill
178- For /console/inspect tree traversal and schema generation: see the `routeros-command-tree` skill
179- For running CHR in QEMU (local or CI): see the `routeros-qemu-chr` skill
180- For packet capture, /tool/sniffer, and TZSP streaming: see the `routeros-sniffer` skill
181
182**MCP tools:**
183
184- For command tree browsing and property lookups: use the `rosetta` MCP server tools (`routeros_search`, `routeros_get_page`, `routeros_command_tree`)