Reset Configuration

Reset Configuration

Version Info

RouterOS 7.16 | Min: v6.0+ | ⏱️ 5 minutes | 🟢 Beginner

Tested on: 7.16 7.14

Version-specific notes

• v7.13: License agreement prompt appears after reset
• v7.0: Menu path changed from /system reset-configuration to /system/reset-configuration
• v6.x: Use /system reset-configuration (without slash separators)

TL;DR (Quick Start)

For the impatient: reset to factory defaults with one command.

/system/reset-configuration
# Confirm with 'y' when prompted

For a completely empty configuration (no defaults):

/system/reset-configuration no-defaults=yes skip-backup=yes

After reset, connect to 192.168.88.1 via any LAN port (not ether1/WAN).

Overview

What this does: Reset Configuration clears the router’s configuration and optionally restores factory defaults. This can be done via CLI command, GUI, or physical reset button.

When to use this:

• Restoring a misconfigured router to a known good state
• Preparing a router for a new deployment
• Clearing all settings before selling or repurposing
• Recovering from configuration mistakes that lock you out
• Deploying custom configurations via run-after-reset scripts

Prerequisites:

• CLI access (SSH, console, or WinBox terminal) OR physical access to reset button
• Knowledge that this will disconnect your current session
• Backup of current configuration if needed

Configuration Steps

Step 1: Backup Current Configuration (Optional)

Before resetting, save your current configuration:

/system/backup save name=before-reset

Check the backup file exists:

/file print where name~"before-reset"

Step 2: Reset to Factory Defaults

Execute the reset command:

/system/reset-configuration

Confirmation prompt:

Dangerous! Reset anyway? [y/N]:

Type y and press Enter. The router will reboot with the default configuration.

Expected result after reboot:

• Default IP: 192.168.88.1 on LAN interface (typically bridge)
• Admin user: admin (password on sticker or empty on older devices)
• DHCP server: Pool 192.168.88.10-254
• Basic firewall and NAT on WAN interface (ether1)

Step 3: Connect After Reset

After reset completes (~30-60 seconds for reboot):

1. Connect your computer to any port except ether1 (which is WAN by default)
2. Set your computer to obtain IP automatically (DHCP)
3. Access 192.168.88.1 via browser or WinBox
4. Login as admin with the password from the device sticker (or blank)

Common Scenarios

Scenario: Reset to Empty Configuration

Remove all configuration without loading defaults. Useful for starting completely fresh:

/system/reset-configuration no-defaults=yes skip-backup=yes

After reset:

• All interfaces disabled
• No IP addresses assigned
• No firewall rules
• Access via MAC-WinBox or serial console only

Scenario: Keep User Accounts

Reset configuration but preserve user accounts and passwords:

/system/reset-configuration keep-users=yes

Useful when you want to clear the config but maintain admin access.

Scenario: Reset with Custom Script

Deploy a custom configuration automatically after reset:

# First, upload your script to the router
# /file print should show restore.rsc

# Then reset with script execution
/system/reset-configuration no-defaults=yes run-after-reset=restore.rsc

Script template (restore.rsc):

# Add delay for interface initialization
:delay 15s

# Your configuration commands
/interface/bridge add name=bridge1
/ip/address add address=192.168.1.1/24 interface=bridge1
/ip/dhcp-server/network add address=192.168.1.0/24 gateway=192.168.1.1

:log info "Configuration restore complete"

Scenario: Enable CAPs Mode

Reset and configure as a CAPsMAN-controlled access point:

/system/reset-configuration caps-mode=yes

The router will boot as a CAP, looking for a CAPsMAN controller via DHCP option or broadcast.

Scenario: Physical Reset Button (Factory Reset)

When CLI access is unavailable:

1. Power off the router
2. Press and hold the reset button
3. Power on while holding the button
4. Wait for LED to start flashing (~5 seconds)
5. Release the button immediately when LED flashes
6. Router reboots with default configuration

Scenario: Physical Reset Button (Netinstall Mode)

For complete RouterOS reinstallation:

1. Power off the router
2. Press and hold the reset button
3. Power on while holding the button
4. Wait for LED to flash, then turn solid, then turn off (~15 seconds)
5. Release button when LED turns off
6. Router enters Netinstall mode (awaiting Netinstall server)

Physical Reset Button Reference

Hold Duration	LED State	Action
~3 seconds (before power)	-	Load backup RouterBOOT bootloader
~5 seconds	Flashing	Factory reset (load default configuration)
~10 seconds	Solid	Enable CAPs mode
~15 seconds	Off	Enter Netinstall/Etherboot mode

Default Configurations by Device Type

Device Type	WAN Interface	LAN Configuration	Features
AP Router	ether1 (DHCP client, firewall)	Bridge (remaining ports + wireless), 192.168.88.1/24	DHCP server, NAT, DNS
CPE Router	wlan1 (DHCP client, firewall)	Bridge (Ethernet ports), 192.168.88.1/24	DHCP server, NAT
LTE CPE	LTE (firewall)	Bridge (Ethernet + wireless), 192.168.88.1/24	DHCP server, NAT
Switch	-	Bridge (all ports), 192.168.88.1/24	Layer 2 switching
CAP	ether1 (DHCP client)	Bridge (remaining ports), CAPsMAN-managed wireless	Controlled AP

View your device’s default configuration:

/system/default-configuration print

Verification

Confirm the reset completed successfully:

Check 1: Verify Default IP

/ip/address print

Expected: Shows 192.168.88.1/24 on bridge or LAN interface.

Check 2: Verify Default Route (AP Routers)

/ip/route print

Expected: For AP routers, shows DHCP-assigned default route via ether1.

Check 3: Check Backup File

/file print where name~"backup"

Expected: Auto-backup file present (unless skip-backup=yes was used).

Check 4: Verify DHCP Server Running

/ip/dhcp-server print

Expected: DHCP server enabled on bridge interface.

Troubleshooting

Symptom	Cause	Solution
Cannot connect after reset	Connected to WAN port (ether1)	Connect to any other port; ether1 is WAN by default
Cannot connect after reset	IP not 192.168.88.x	Set computer to DHCP or manually use 192.168.88.2/24
Run-after-reset script not executing	Script errors or timing	Add :delay 15s at script start; test with /import first
Run-after-reset script timeout	Script exceeds 2-minute limit	Optimize script; split into multiple scripts
”Interface not ready” in script	Interfaces not initialized	Add delay or wait loop: :while ([/interface find name=wlan1] = "") do={:delay 1s}
Wrong reset mode (Netinstall instead of factory)	Held button too long	Release button AS SOON AS LED starts flashing (~5 seconds)
CAPs mode instead of factory reset	Held button ~10 seconds	Release during flashing phase, not solid LED phase
Some settings persist after reset	Used reset without no-defaults	Use no-defaults=yes skip-backup=yes for complete clear
Reset button doesn’t work	Protected Bootloader enabled	Must use CLI reset or contact MikroTik support
Storage full with backup files	Repeated resets create backups	Use skip-backup=yes or periodically clean old backups

Common Mistakes

• Don’t release the reset button too late - Different hold durations trigger different modes (factory reset vs CAPs vs Netinstall)
• Don’t forget the 2-minute script timeout - Run-after-reset scripts must complete within 2 minutes
• Don’t skip the delay in run-after-reset scripts - Interfaces need time to initialize; add :delay 15s at the start
• Don’t connect to ether1 after reset - It’s configured as WAN by default; use other ports
• Don’t use no-defaults without a plan - An empty configuration means no IP address; you’ll need MAC-WinBox or console access

Community Tips

Testing run-after-reset scripts: Always test your script with /import before using it with reset:

/import restore.rsc

Interface name changes: Interface names may change after reset (wlan1 vs wlan2). Use interface discovery in scripts:

:local wlanInt [/interface/wireless find where default-name~"wlan"]

Preserving passwords: User passwords cannot be exported (security measure). Use keep-users=yes or manually recreate users in your script.

Netinstall reformats storage: Using Netinstall (15-second hold) erases everything including User Manager and Dude databases. Use CLI reset to preserve files.

Reset vs Netinstall Comparison

Aspect	Reset Configuration	Netinstall
Configuration	Cleared or defaulted	Cleared completely
RouterOS	Preserved	Reinstalled
License	Preserved	Preserved
Files	Preserved (unless format)	Lost (drive formatted)
User Manager DB	Preserved	Lost
Dude DB	Preserved	Lost
SSH Keys	Preserved (unless no-defaults)	Lost
Access Required	CLI/GUI/Button	Physical + Netinstall server

Related Topics

• System Backup and Restore - Binary backup and restore operations
• Quick Set Initial Configuration - Simplified initial setup wizard
• User Management - Managing admin accounts
• RouterBOARD Settings - Bootloader and hardware settings

Reference

• MikroTik Reset Button Documentation
• MikroTik Configuration Management
• MikroTik Default Configurations
• Version changes:
  • v7.13: License agreement prompt after reset
  • v7.0: Menu path syntax changed (use /system/reset-configuration)

Key Properties Reference

Property	Type	Default	Description
no-defaults	yes/no	no	Clear configuration without loading defaults (empty config)
skip-backup	yes/no	no	Skip automatic backup file generation before reset
keep-users	yes/no	no	Preserve existing user accounts during reset
run-after-reset	filename	-	Execute specified .rsc script file after reset
caps-mode	yes/no	no	Enable CAPs mode (CAPsMAN controlled AP) after reset

Command Reference

Command	Description
/system/reset-configuration	Reset router configuration
/system/default-configuration print	View default configuration template
/system/backup save	Create binary backup before reset
/file print	List files including backups and scripts
/import	Test a script before using with run-after-reset

Summary

Reset Configuration restores your MikroTik router to factory defaults or a custom state:

1. CLI reset - /system/reset-configuration with optional parameters
2. Physical reset - Hold button ~5 seconds until LED flashes, then release
3. Custom deployment - Use run-after-reset with a script for automated configuration

Key points:

• Default IP after reset is 192.168.88.1 on LAN ports (not ether1)
• Ether1 is WAN by default on AP routers; connect to other ports
• Add :delay 15s at the start of run-after-reset scripts
• Scripts have a 2-minute execution timeout
• Button hold duration matters: ~5s = factory reset, ~10s = CAPs, ~15s = Netinstall
• Use no-defaults=yes skip-backup=yes for a completely empty configuration
• Netinstall reformats storage; use CLI reset to preserve files