Essential MikroTik Commands Every Network Engineer Should Know

Accessing the CLI

You can access the MikroTik CLI through several methods:

• SSH: Securely log in remotely with: ssh admin@<router-ip>
• Telnet: Use in controlled environments: telnet <router-ip>
• WinBox Terminal: Use the built-in terminal in WinBox.
• Console Port: Direct access via a serial cable for initial setups or recovery scenarios.

Basic Navigation

Once connected, navigate the CLI using these commands:

• / – Returns you to the root of the configuration tree.
• .. – Moves up one level in the configuration hierarchy.
• ? – Displays help for the current context (e.g., /interface ?).

Command Syntax and Auto-Completion

MikroTik commands follow a consistent structure:

/path/to/command action [parameters]

For example, to list all interfaces:

/interface print

Use the Tab key for auto-completion and type ? to display available parameters. This helps speed up command entry and reduces errors.

Tips for First-Time Users

• Export Configurations: Use the /export command to print your current configuration and understand how GUI settings translate into CLI commands.
• Experiment in a Lab Environment: Use a spare router or virtual lab solutions such as GNS3 or Eve-NG to practice without risking production systems.

Interface Management

• List Interfaces: /interface print
• Enable/Disable an Interface: Enable with /interface enable ether1 and disable with /interface disable ether1
• Monitor Interface Status: Use /interface ethernet monitor ether1 to view real-time statistics.

IP Address Configuration

• Add an IP Address: Example: /ip address add address=192.168.1.1/24 interface=ether1
• List IP Addresses: /ip address print

Routing

• Add a Static Route: /ip route add dst-address=192.168.2.0/24 gateway=192.168.1.1
• View the Routing Table: /ip route print
• Monitor a Specific Route: /ip route monitor [id]

Firewall Rules

• Add a Firewall Rule: Example: /ip firewall filter add chain=input action=accept protocol=tcp dst-port=22
• List Firewall Rules: /ip firewall filter print

NAT Configuration

• Configure NAT: Enable NAT for outbound traffic with /ip firewall nat add chain=srcnat action=masquerade
• View NAT Rules: /ip firewall nat print

Port Security

Isolate ports to enhance security. For example:

• /interface bridge port set ether3 horizon=1

System Monitoring

• Check CPU and Memory Usage: /system resource print
• Monitor Real-Time Traffic: /interface monitor-traffic ether1

Logs and Diagnostics

• View System Logs: /log print
• Ping Test: /tool ping 8.8.8.8
• Traceroute: /tool traceroute google.com

Packet Sniffing

• Quick Packet Capture: /tool sniffer quick
• Advanced Capture Options: Adjust filters and export settings as needed for in-depth analysis.

DHCP Server/Client Setup

• Configure a DHCP Server: /ip dhcp-server setup
• Check DHCP Client Status: /ip dhcp-client print

VPN Configuration

• Set Up a PPTP VPN Client: /interface pptp-client add connect-to=VPN_Server_IP user=username password=password
• Set Up an L2TP VPN Client: /interface l2tp-client add connect-to=VPN_Server_IP user=username password=password

QoS and Traffic Shaping

• Configure a Simple Queue: /queue simple add name="User1" target=192.168.1.100 max-limit=10M/10M

Scripting and Automation

MikroTik’s scripting capabilities allow you to automate routine tasks:

• Backup Script Example: /system backup save name=auto_backup_$(/system clock get date)
• Schedule a Task: /system scheduler add name="DailyBackup" interval=24h on-event="/system backup save name=backup_$(/system clock get date)"
• Simple Monitoring Script: Example:

  :if ([/system resource get cpu-load] > 80) do={
    /log warning "High CPU load detected!"
  }

Backup and Restore

• Create a Backup: /system backup save name=backup_YYYYMMDD
• Restore a Backup: /system backup load name=backup_YYYYMMDD

Firmware Updates

• Check for Updates: /system package update check-for-updates
• Install Updates: /system package update install

Scheduling Maintenance Tasks

• Schedule Regular Backups: /system scheduler add name="WeeklyBackup" interval=7d on-event="/system backup save name=weekly_backup_$(/system clock get date)"
• Automate Update Checks: /system scheduler add name="UpdateCheck" interval=24h on-event="/system package update check-for-updates"