RouterOS

https://help.mikrotik.com/docs/spaces/ROS/
Admin
RouterOS is the operating system for MikroTik devices that provides routing, networking, and system...
Tokens:1,341,313
Snippets:9,194
Trust Score:10
Update:6 days ago
Show doc for...
Tokens:
Raw
### Container log output on start

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/169246787/Container%2B-%2Bmosquitto%2BMQTT%2Bserver

Example log output after starting the mosquitto container, showing version, config load, and listening sockets.

```log
 12:12:46 container,info,debug 1707214366: mosquitto version 2.0.18 starting  12:12:46 container,info,debug 1707214366: Config loaded from /mosquitto/config/mosquitto.conf.  12:12:46 container,info,debug 1707214366: Opening ipv4 listen socket on port 1883.  12:12:46 container,info,debug 1707214366: Opening ipv6 listen socket on port 1883.  12:12:46 container,info,debug 1707214366: mosquitto version 2.0.18 running
```

--------------------------------

### Run DHCP server setup command

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/24805500/DHCP

Starts the interactive DHCP server setup wizard, which prompts for interface, network, gateway, address pool, DNS servers, and lease time.

```routeros
/ip dhcp-server setup  Select interface to run DHCP server on   dhcp server interface: ether3 Select network for DHCP addresses   dhcp address space: 192.168.88.0/24 Select gateway for given network   gateway for dhcp network: 192.168.88.1 Select pool of ip addresses given out by DHCP server   addresses to give out: 192.168.88.2-192.168.88.254 Select DNS servers   dns servers: 10.155.126.1,10.155.0.1,                                Select lease time   lease time: 10m
```

--------------------------------

### HotSpot setup interactive command

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/56459266/HotSpot%2B-%2BCaptive%2Bportal

Runs the /ip hotspot setup command, prompting for interface, local address, masquerade, address pool, SSL certificate, SMTP server, DNS servers, DNS name, and local hotspot user. The example uses ether3, 10.5.50.1/24, pool 10.5.50.2-10.5.50.254, no certificate, SMTP 0.0.0.0, DNS 10.1.101.1, DNS name myhotspot, and user admin.

```routeros
[admin@MikroTik] /ip hotspot> setup  Select interface to run HotSpot on   hotspot interface: ether3 Set HotSpot address for interface   local address of network: 10.5.50.1/24 masquerade network: yes Set pool for HotSpot addresses   address pool of network: 10.5.50.2-10.5.50.254 Select hotspot SSL certificate   select certificate: none Select SMTP server   ip address of smtp server: 0.0.0.0 Setup DNS configuration   dns servers: 10.1.101.1 DNS name of local hotspot server   dns name: myhotspot Create local hotspot user   name of local hotspot user: admin password for the user:  [admin@MikroTik] /ip hotspot>
```

--------------------------------

### Print container status and enable start-on-boot (7.6beta6+)

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/84901929/Container

Print container details (including ID, tag, interface, root-dir) and set the container with ID 0 to start on boot. The shown output displays an example status.

```routeros
/container/print  0 name="2e679415-2edd-4300-8fab-a779ec267058" tag="test_arm64:latest" os="linux" arch="arm" interface=veth2     root-dir=disk1/alpine mountslists="" dns="" logging=yes start-on-boot=yes status=running   /container/set 0 start-on-boot=yes
```

--------------------------------

### Navigate to certificate directory and list files

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/166920348/Container%2B-%2BThingsBoard%2BMQTT%2BHTTP%2Bserver

Navigate to the directory containing the certificates (keystore.p12 and mqttserver.p12) and list its contents with dir. This is the starting point for the SFTP download steps.

```cmd
C:\Windows\System32>cd c:\Users\Admin\Desktop\ThingsBoard
C:\Users\Admin\Desktop\ThingsBoard>dir
Directory of C:\Users\Admin\Desktop\ThingsBoard

  27.01.2023  15:36    <DIR>          .
  27.01.2023  15:36    <DIR>          ..
  27.01.2023  15:09             2 448 keystore.p12
  27.01.2023  15:36             2 434 mqttserver.p12
               2 File(s)          4 882 bytes
               2 Dir(s)  51 380 154 368 bytes free
```

--------------------------------

### YAML Example: Alpine Linux iperf3 Server

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/343244823/Apps

Compose YAML file for a custom app running Alpine Linux with iperf3 server. Defines service 'iperf' using docker.io/alpine:latest, exposes TCP and UDP ports 5201, and runs a shell command to install and start iperf3.

```yaml
name: alpine-iperf
descr: Alpine Linux container running iperf3 server
page: https://iperf.fr/
category: network
default-credentials: none
services:
  iperf:
    image: docker.io/alpine:latest
    ports:
      - 5201:5201:tcp
      - 5201:5201:udp
    command: /bin/sh -c "apk add --no-cache iperf3 && iperf3 -s"
```

--------------------------------

### Print follow with on-event Example

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/47579229/Scripting

Example of using the on-event parameter with follow to run scripts when new entries appear.

```routeros
/log print follow on-event={:log info "Someone logged-in"} where message~"admin logged"
```

--------------------------------

### find operator example

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/47579229/Scripting

Returns the position of a substring or array element. The example finds the first occurrence of "a" in "abc" starting from index -1.

```routeros
:put [:find "abc" "a" -1];
```

--------------------------------

### Usage examples for python_api_minimal.py

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/47579209/Python3%2BExample

Shows how to run the script with different IP addresses, usernames, passwords, and commands. The first example uses an empty password, the second uses a secret password.

```bash
python3 python_api_minimal.py 192.168.88.1 admin "" /system/resource/print
```

```bash
python3 python_api_minimal.py 10.0.0.1 admin secret /interface/print
```

--------------------------------

### RouterOS /openflow/flow print detail output

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/295239685/Openflow

Example output from the /openflow/flow menu showing installed flows with match and action details. Useful for verifying that Faucet has installed the expected flows.

```routeros
[admin@CCR2004_2XS_111] /openflow/flow>  print detail  Flags: I - inactive   0   switch=faucet version=4 match=" [ { ethdst_m=01000cccccccffffffffffff } ]" actions=" []"       info="priority 8240, idletimeout 0, hardtimeout 0, cookie 1524372928, removenotify 0" table-id=4    1   switch=faucet version=4 match=" [ { ethdst_m=01000ccccccdffffffffffff } ]" actions=" []"       info="priority 8240, idletimeout 0, hardtimeout 0, cookie 1524372928, removenotify 0" table-id=4    2   switch=faucet version=4 match=" [ { ethdst_m=ffffffffffffffffffffffff }; { vlanvid=1064 } ]"       actions=" [ { apply-actions= [ { popvlan={} }; { output={ port=1; max_len=0 } }; { output={ port=2; max_len=0 } } ]          } ]"       info="priority 8240, idletimeout 0, hardtimeout 0, cookie 1524372928, removenotify 0" table-id=4    3   switch=faucet version=4 match=" [ { ethdst_m=0180c2000000fffffffffff0 } ]" actions=" []"       info="priority 8236, idletimeout 0, hardtimeout 0, cookie 1524372928, removenotify 0" table-id=4    4   switch=faucet version=4 match=" [ { ethdst_m=0180c2000000ffffff000000 }; { vlanvid=1064 } ]"       actions=" [ { apply-actions= [ { popvlan={} }; { output={ port=1; max_len=0 } }; { output={ port=2; max_len=0 } } ]          } ]"       info="priority 8216, idletimeout 0, hardtimeout 0, cookie 1524372928, removenotify 0" table-id=4    5   switch=faucet version=4 match=" [ { ethdst_m=01005e000000ffffff000000 }; { vlanvid=1064 } ]"       actions=" [ { apply-actions= [ { popvlan={} }; { output={ port=1; max_len=0 } }; { output={ port=2; max_len=0 } } ]          } ]"       info="priority 8216, idletimeout 0, hardtimeout 0, cookie 1524372928, removenotify 0" table-id=4    6   switch=faucet version=4 match=" [ { ethdst_m=333300000000ffff00000000 }; { vlanvid=1064 } ]"       actions=" [ { apply-actions= [ { popvlan={} }; { output={ port=1; max_len=0 } }; { output={ port=2; max_len=0 } } ]          } ]"       info="priority 8208, idletimeout 0, hardtimeout 0, cookie 1524372928, removenotify 0" table-id=4    7   switch=faucet version=4 match=" [ { vlanvid=1064 } ]"       actions=" [ { apply-actions= [ { popvlan={} }; { output={ port=1; max_len=0 } }; { output={ port=2; max_len=0 } } ]          } ]"       info="priority 8192, idletimeout 0, hardtimeout 0, cookie 1524372928, removenotify 0" table-id=4    8   switch=faucet version=4 match=" []" actions=" []"       info="priority 0, idletimeout 0, hardtimeout 0, cookie 1524372928, removenotify 0" table-id=4    9   switch=faucet version=4 match=" []" actions=" [ { goto=4 } ]"       info="priority 0, idletimeout 0, hardtimeout 0, cookie 1524372928, removenotify 0" table-id=3   10   switch=faucet version=4 match=" [ { ethtype=9000 } ]" actions=" []"       info="priority 20490, idletimeout 0, hardtimeout 0, cookie 1524372928, removenotify 0" table-id=2   11   switch=faucet version=4 match=" [ { vlanvid=1064 } ]"       actions=" [ { apply-actions= [ { output={ port=4294967293; max_len=96 } } ] }; { goto=3 } ]"       info="priority 4096, idletimeout 0, hardtimeout 0, cookie 1524372928, removenotify 0" table-id=2   12   switch=faucet version=4 match=" []" actions=" [ { goto=3 } ]"       info="priority 0, idletimeout 0, hardtimeout 0, cookie 1524372928, removenotify 0" table-id=2   13   switch=faucet version=4 match=" [ { inport=00000001 }; { vlanvid=0000 } ]"       actions=" [ { apply-actions= [ { pushvlan={ ethertype=33024 } }; { setfield={ vlanvid=1064 } } ] }; { goto=2 } ]"       info="priority 4096, idletimeout 0,
```

--------------------------------

### Run Netinstall version 7 with empty config and no branding

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/24805390/Netinstall

Runs Netinstall version 7 with -e (empty config) and -b (remove branding) flags. Includes the expected output showing the boot image, branding detection, and package sending.

```bash
admin@ubuntu:~$ sudo ./netinstall-cli -e -b -i enx1234567ee890 -a 192.168.88.3 routeros-7.14.2-arm.npk wireless-7.14.2-arm.npk 
Version: 7.15beta9(2024-03-27 20:41:15)
Will apply empty config
Will remove branding
Using Interface: enx1234567ee890
Wait for Link-UP on 'enx1234567ee890'. OK
Using Client IP: 192.168.88.3
Using Server IP: 192.168.88.10
Starting PXE server
Waiting for RouterBOARD...
client: 74:4D:28:8E:86:74
Detected client architecture: arm
Sending and starting Netinstall boot image ... 
Installed branding package detected
Discovered RouterBOARD... 74:4D:28:8E:86:74
Formatting...
Sending package routeros-7.14.2-arm.npk ...
Sending package wireless-7.14.2-arm.npk ...
Sending empty config ...
Ready for reboot...
Sent reboot command
```

--------------------------------

### Print eSIM profiles

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/30146563/LTE%2B5G

Lists the eSIM profiles installed on the eSIM. The output shows flags, columns, and example profiles.

```routeros
/interface/lte esim print  
Flags: A - ACTIVE  
Columns: INTERFACE, NAME, SPN, ICCID, NICKNAME  
#   INTERFACE  NAME           SPN                   ICCID   NICKNAME  
0 A lte1       NAME1          SPN1    1111111111111111111   nickname1  
1   lte1       NAME2          SPN2    2222222222222222222   nickname2  
2   lte1       NAME3          SPN3    3333333333333333333   nickname3
```

--------------------------------

### Verify VRRP connection tracking sync in logs

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/81362945/VRRP

Example log output showing VRRP becoming MASTER and starting CONNTRACK synchronization.

```log
16:14:06 vrrp,info vrrp1 now MASTER, master down timer
16:14:06 vrrp,info vrrp1 stop CONNTRACK
16:14:06 vrrp,info vrrp1 starting CONNTRACK MASTER
```

--------------------------------

### GET specific properties with .proplist

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST%2BAPI

Uses the '.proplist' parameter to return only specific properties. This example shows only the address and disabled properties for all IP addresses.

```bash
$ curl -k -u admin: https://10.155.101.214/rest/ip/address?.proplist=address,disabled
```

--------------------------------

### GET interface by name with curl

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST%2BAPI

If the table contains named parameters, the name can be used instead of the ID. This example fetches the ether1 interface from /rest/interface/ether1.

```bash
$ curl -k -u admin: https://10.155.101.214/rest/interface/ether1
```

--------------------------------

### Run Netinstall CLI

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/24805390/Netinstall

Runs the Netinstall CLI tool. Requires root privileges (use sudo). Replace [parameters], [address/interface], and [package VERSION] with actual values.

```bash
sudo ./netinstall-cli [-parameters] [address/interface] routeros-arm64-[package VERSION].npk
```

--------------------------------

### Example hosts file content

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/37748767/DNS

Example content for a local adlist file. Each line maps a domain to 0.0.0.0. The hostname format must match this format when using a local file.

```text
0.0.0.0 example1.com
0.0.0.0 eu1.example.com
0.0.0.0 ex.com
0.0.0.0 com.example.com
```

--------------------------------

### Comment syntax example

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/47579229/Scripting

Shows comment syntax: a comment starts with # and ends at the end of the physical line. A # inside a string is not a comment. Multiline comments are not supported.

```routeros
# this is a comment  # next line comment :global a; # another valid comment  :global myStr "part of the string # is not a comment"
```

--------------------------------

### GET filtered IP addresses with query parameters

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST%2BAPI

Filters the output using query parameters. This example returns only valid addresses that belong to the 10.155.101.0 network and are dynamic.

```bash
$ curl -k -u admin: "https://10.155.101.214/rest/ip/address?network=10.155.101.0&dynamic=true"
```

--------------------------------

### Navigate to ip route menu and print

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/8978498/Console

Shows how to move into the 'ip route' menu level and then execute the 'print' command. The prompt changes to reflect the current menu level.

```text
[admin@MikroTik] > ip route  [admin@MikroTik] ip route> print  Flags: X - disabled, A - active, D - dynamic,  C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,  B - blackhole, U - unreachable, P - prohibit #  DST-ADDRESS PREF-SRC G GATEWAY DIS INTE...  0 A S 0.0.0.0/0 r 10.0.3.1 1 bridge1  1 ADC 1.0.1.0/24 1.0.1.1 0 bridge1  2 ADC 1.0.2.0/24 1.0.2.1 0 ether3  3 ADC 10.0.3.0/24 10.0.3.144 0 bridge1  4 ADC 10.10.10.0/24 10.10.10.1 0 wlan1 [ admin@MikroTik] ip route>
```

--------------------------------

### GET a single IP address by ID with curl

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/47579162/REST%2BAPI

Returns a single record by appending the ID at the end of the URL. The example fetches the record with ID *1 from /rest/ip/address.

```bash
$ curl -k -u admin: https://10.155.101.214/rest/ip/address/*1
```

--------------------------------

### /system/package/getall response

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/47579160/API

Example of the /system/package/getall command returning a series of !re sentences for each package, followed by !done. Shows the format of package properties such as id, disabled, name, version, build-time, and scheduled.

```plaintext
/system/package/getall
---


!re
=.id=*5802
=disabled=no
=name=routeros-x86
=version=3.0beta2
=build-time=oct/18/2006 16:24:41
=scheduled=


!re
=.id=*5805
=disabled=no
=name=system
=version=3.0beta2
=build-time=oct/18/2006 17:20:46
=scheduled=


... more !re sentences ...
!re
=.id=*5902
=disabled=no
=name=advanced-tools
=version=3.0beta2
=build-time=oct/18/2006 17:20:49
=scheduled=


!done
```

--------------------------------

### Define and run a function with arguments

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/47579229/Scripting

Shows how to define and run a function using :global and the do={} syntax, and how to pass arguments either by name (a) or positionally (1). The output demonstrates both argument-passing methods.

```routeros
#define function and run it
:global myFunc do={:put "hello from function"}
$myFunc

output:
hello from function

#pass arguments to the function
:global myFunc do={:put "arg a=$a"; :put "arg '1'=$1"}

$myFunc a="this is arg a value" "this is arg1 value"

output:
arg a=this is arg a value
arg '1'=this is arg1 value
```

--------------------------------

### RouterOS scheduler and script setup for Btrfs RAID monitoring

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/295239711/Btrfs

This RouterOS command creates scheduled tasks and scripts to start and monitor Btrfs balance and scrub operations. It schedules balance and scrub start calls, status checks, and a health check, along with scripts that initiate the operations and log their progress.

```routeros
/system scheduler add interval=1w30s name=BraidBalanceStartCall on-event=BraidBalanceStart policy=ftp,read,write,policy,test,sniff start-date=1970-01-01 start-time=01:00:00 add interval=1w30s name=BraidScrubStartCall on-event=BraidScrubStart policy=ftp,read,write,policy,test,sniff start-date=1970-01-01 start-time=02:00:00 add interval=2m name=BraidBalanceStatusCheckCall on-event=BraidBalanceStatus policy=ftp,read,write,policy,test,sniff start-time=startup add interval=2m name=BraidScrubStatusCheckCall on-event=BraidScrubStatus policy=ftp,read,write,policy,test,sniff start-time=startup add interval=30s name=BraidHealthCheckCall on-event=BraidHealthCheck policy=ftp,read,write,policy,test,sniff start-time=startup add interval=2m name=BraidReplaceStatusCheckCall on-event=BraidReplaceStatus policy=ftp,read,write,policy,test,sniff start-time=startup  /system script add dont-require-permissions=no name=BraidScrubStart owner=admin policy=ftp,read,write,policy,test,sniff source=":global btrfsscrubstatuscheck;\     \nif (\$btrfsscrubstatuscheck != \"started\") do={\     \n  :set \$btrfsscrubstatuscheck (\$btrfsscrubstatuscheck \"started\");\     \n  foreach i in=[/disk/btrfs/filesystem/find] do={ /disk/btrfs/filesystem/scrub-start \$i;\     \n    :local temp [ /disk btrfs filesystem/get value-name=label \$i;]\     \n    /log info message=\"INFO: Btrfs scrub process started on  \$temp\";\     \n    :delay 3; \     \n  }\     \n}\     \n" add dont-require-permissions=no name=BraidBalanceStart owner=admin policy=ftp,read,write,policy,test,sniff source=":global btrfsbalancestatuscheck;\     \nif (\$btrfsbalancestatuscheck != \"started\") do={\     \n:set \$btrfsbalancestatuscheck (\$btrfsbalancestatuscheck \"started\");\     \n:local percentage;\     \n:set \$percentage (\$percentage 50);\     \n  foreach i in=[/disk/btrfs/filesystem/find] do={ /disk/btrfs/filesystem/balance-start data-usage=\$percentage \$i;\     \n    :local temp [ /disk btrfs filesystem/get value-name=label \$i;]\     \n    /log info message=\"INFO: Btrfs balance process started on  \$temp\";\     \n    :delay 3; \     \n  }\     \n}" add dont-require-permissions=no name=BraidBalanceStatus owner=admin policy=ftp,read,write,policy,test,sniff source=":global btrfsbalancestatuscheck;\     \nif (\$btrfsbalancestatuscheck = \"started\") do={\     \n:local arraycnt [/disk/btrfs/filesystem/print count-only as-value];\     \n:local counter [:set \$counter (\$counter 0)];\     \n:local counterdiff [:set \$counterdiff (\$counterdiff 0)];\     \n  foreach i in=[/disk/btrfs/filesystem/find] do={ \     \n    :local barray [ /disk btrfs filesystem/get value-name=balance-status  \$i;]\     \n    :local temp [ /disk btrfs filesystem/get value-name=label \$i;]\     \n    if ( \$barray != \"done\" and \$btrfsbalancestatuscheck = \"started\") do={\     \n        /log info message=\"INFO: Btrfs current balance status on  \$temp is \$barray\";\     \n    }\     \n    if ( \$barray = \"done\" and \$btrfsbalancestatuscheck = \"started\") do={\     \n      :set \$counter (\$counter +1);\     \n      :set \$counterdiff (\$arraycnt - \$counter);\     \n      if (\$counterdiff =1) do={\     \n        /log info message=\"INFO: Btrfs balancing already done on \$counter arrays\";\     \n      }\     \n    }\     \n    if ( \$counter = \$arraycnt) do={\     \n      /log info message=\"INFO: Btrfs array balance status on  \$temp is \$barray \";\     \n      :set \$btrfsbalancestatuscheck (\$btrfsbalancestatuscheck \"done\");\     \n    }\     \n  } \     \n}" add dont-require-permissions=no name=BraidScrubStatus owner=admin policy=ftp,read,write,policy,test,sniff source=":global btrfsscrubstatuscheck;\     \nif (\$btrfsscrubstatuscheck = \"started\") do={\     \n:local arraycnt [/disk/btrfs/filesystem/print count-only as-value];\     \n:local counter [:set \$counter (\$counter 0)];\     \n:local counterdiff [:set \$counterdiff (\$counterdiff 0)];\     \n  foreach i in=[/disk/btrfs/filesystem/find] do={ \     \n    :local barray [ /disk btrfs filesystem/get value-name=scrub-status  \$i;]\     \n    :local temp [ /disk btrfs filesystem/get value-name=label \$i;]\     \n    if ( \$barray != \"done\" and \$btrfsscrubstatuscheck = \"started\") do={\     \n      /log info message=\"INFO: Btrfs current scrub status on  \$temp is \$barray\";\     \n    }\     \n    if ( \$barray = \"done\" and \$btrfsscrubstatuscheck = \"started\") do={\     \n      :set \$counter (\$counter +1);\     \n      :set \$counterdiff (\$arraycnt - \$counter);\     \n      if (\$counterdiff =1) do={\     \n        /log info message=\"INFO: Btrfs scrubbing already done on \$counter arrays\";\     \n      }\     \n    }\     \n    if ( \$counter = \$arraycnt ) do={\     \n      /log info message=\"INFO: Btrfs 
```

--------------------------------

### Print follow with timestamp Example

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/47579229/Scripting

Example of using the timestamp parameter with follow to highlight the time when changes are made.

```routeros
/ip arp print follow timestamp
```

--------------------------------

### Successful LoRa connection log output

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/16351619/General%2BProperties

Example log output showing a successful connection to The Things Network, including the forwarder starting, connecting to the LNS, and becoming ready.

```text
 13:50:33 lora,info gateway-0 forwarder started
 13:50:38 lora,info [LNS] connecting to wss://eu1.cloud.thethings.network:8887/router-info
 13:50:39 lora,info [LNS] eu1.cloud.thethings.network discovered
 13:50:39 lora,info [LNS] eu1.cloud.thethings.network disconnected
 13:50:39 lora,info [LNS] connecting to wss://eu1.cloud.thethings.network:8887/traffic/eui-xxxx
 13:50:39 lora,info [LNS] eu1.cloud.thethings.network configured
 13:50:52 lora,info gateway-0 forwarder is ready
```

--------------------------------

### Command concatenation with square brackets

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/47579229/Scripting

Demonstrates command concatenation using square brackets. The example contains three command lines: :put, /ip route get, and find gateway=1.1.1.1.

```routeros
:put [/ip route get [find gateway=1.1.1.1]]; 
```

--------------------------------

### Run API client with login and user/getall commands

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/47579160/API

Command-line invocation of the example Python3 API client (api.py) with arguments for host, user, and password, followed by the expected output showing login response and user/getall results.

```bash
debian@localhost:~/api-test$ ./api.py 10.0.0.1 admin '' <<< /login <<<  >>> !done >>> =ret=93b438ec9b80057c06dd9fe67d56aa9a >>>  <<< /login <<< =name=admin <<< =response=00e134102a9d330dd7b1849fedfea3cb57 <<<  >>> !done >>>  /user/getall  <<< /user/getall <<<  >>> !re >>> =.id=*1 >>> =disabled=no >>> =name=admin >>> =group=full >>> =address=0.0.0.0/0 >>> =netmask=0.0.0.0 >>>  >>> !done >>>
```

--------------------------------

### Example debug log output from /log print

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/367919113/Wiliot

Shows the expected debug log entries after enabling wiliot logging, including authorization, registration, token, and MQTT connection steps.

```text
2026-02-12 12:04:54 wiliot,debug [CFG] authorizing...
2026-02-12 12:04:54 wiliot,debug [CFG] authorization complete
2026-02-12 12:04:54 wiliot,debug [CFG] registering...
2026-02-12 12:04:55 wiliot,debug [CFG] registration complete
2026-02-12 12:04:55 wiliot,debug [CFG] polling for token...
2026-02-12 12:04:55 wiliot,debug [CFG] token obtained
2026-02-12 12:04:55 wiliot,debug [CFG] ownerId
2026-02-12 12:04:55 wiliot,debug [CFG] authorization complete
2026-02-12 12:04:55 wiliot,debug [CFG] updating MQTT credentials
2026-02-12 12:04:56 wiliot,debug [CFG] MQTT credentials updated
2026-02-12 12:04:56 wiliot,debug [CFG] connecting to MQTT server
2026-02-12 12:04:56 wiliot,debug [CFG] subscribing to BLE advertaisments
2026-02-12 12:04:56 wiliot,debug [CFG] active
```

--------------------------------

### Show routing table and NAT rules for backup routing example

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/11993097/IPsec

Displays the current routing table and NAT rules to verify the setup before configuring IPsec with a backup routing table.

```routeros
[admin@pair_r1] > /ip route print detail  Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit  0 A S dst-address=0.0.0.0/0 gateway=10.155.107.1 gateway-status=10.155.107.1 reachable via ether1 distance=1 scope=30 target-scope=10 routing-mark=backup   1 A S dst-address=0.0.0.0/0 gateway=172.22.2.115 gateway-status=172.22.2.115 reachable via ether2 distance=1 scope=30 target-scope=10   2 ADC dst-address=10.155.107.0/25 pref-src=10.155.107.8 gateway=ether1 gateway-status=ether1 reachable distance=0 scope=10   3 ADC dst-address=172.22.2.0/24 pref-src=172.22.2.114 gateway=ether2 gateway-status=ether2 reachable distance=0 scope=10   4 ADC dst-address=192.168.1.0/24 pref-src=192.168.1.1 gateway=bridge-local gateway-status=ether2 reachable distance=0 scope=10   [admin@pair_r1] > /ip firewall nat print  Flags: X - disabled, I - invalid, D - dynamic  0 chain=srcnat action=masquerade out-interface=ether1 log=no log-prefix=""   1 chain=srcnat action=masquerade out-interface=ether2 log=no log-prefix=""
```

--------------------------------

### SFP monitor output example

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/8323191/Ethernet

Example output of the /interface ethernet monitor command for an SFP module, showing SFP-specific properties such as temperature, supply voltage, and optical power.

```text
[admin@MikroTik] > /interface ethernet monitor sfp1
                  name: sfp1
                status: link-ok
      auto-negotiation: done
                  rate: 1Gbps
           full-duplex: yes
       tx-flow-control: no
       rx-flow-control: no
             supported: 10M-baseT-half,10M-baseT-full,100M-baseT-half,100M-baseT-full,1G-baseT-half,1G-baseT-full
           advertising: 10M-baseT-half,10M-baseT-full,100M-baseT-half,100M-baseT-full,1G-baseT-half,1G-baseT-full
  link-partner-advertising: 10M-baseT-half,10M-baseT-full,100M-baseT-half,100M-baseT-full,1G-baseT-half,1G-baseT-full
        sfp-temperature: 35C
    sfp-supply-voltage: 3.3V
     sfp-tx-bias-current: 8.5mA
           sfp-tx-power: -2.5dBm
           sfp-rx-power: -3.0dBm
        sfp-wavelength: 1310nm
        sfp-max-power: 1W
        sfp-eeprom-checksum: good
```

--------------------------------

### Create bridge and add ports for protocol-level isolation

Source: https://help.mikrotik.com/docs/spaces/ROS/pages/103841836/CRS1xx%2B2xx%2Bseries%2Bswitches%2Bexamples

Creates a bridge named bridge1 and adds ports ether1 through ether5 with hardware offloading enabled. This is the initial setup for the protocol-level isolation example.

```routeros
/interface bridge add name=bridge1
/interface bridge port add bridge=bridge1 interface=ether1 hw=yes
add bridge=bridge1 interface=ether2 hw=yes
add bridge=bridge1 interface=ether3 hw=yes
add bridge=bridge1 interface=ether4 hw=yes
add bridge=bridge1 interface=ether5 hw=yes
```
Tokens:
Raw