Netinstall

Netinstall

Summary

Netinstall is MikroTik’s dedicated tool for installing and reinstalling RouterOS on devices. Whether you are recovering a corrupted system, performing a clean installation, or resolving software issues that cannot be fixed through normal means, Netinstall provides a reliable method to restore your device to a working state. This documentation covers the complete Netinstall procedure for both Windows and Linux platforms, explains how to place devices into Etherboot mode, and provides troubleshooting guidance for common issues.

The Netinstall process works by booting the device into a special Etherboot mode that allows it to receive RouterOS packages over the network from a connected computer. This approach enables recovery even when the device cannot boot normally from its internal storage. The tool is available as a graphical application for Windows and a command-line utility for Linux, both offering nearly identical functionality. Understanding Netinstall is essential for any MikroTik administrator, as it represents the definitive recovery method when other troubleshooting steps have failed.

Netinstall re-formats the device’s storage during installation, which means all configuration data and saved files are erased. However, the RouterOS license key is preserved, and RouterBOOT settings (such as CPU frequency) remain unchanged. This behavior makes Netinstall safe for recovery purposes without risking license loss or BIOS configuration changes. After installation, the device is reset to default configuration unless you specify otherwise during the process.

Introduction

What is Netinstall?

Netinstall is a network-based installation tool that MikroTik provides for installing RouterOS on their devices. Unlike firmware updates performed through the normal RouterOS interface, Netinstall operates at a lower level by replacing the entire operating system installation on the device’s storage. This capability makes it invaluable for recovering devices that will not boot normally due to corruption, failed updates, or accidental misconfiguration that prevents all access.

The Netinstall architecture consists of two components: the Netinstall server (running on your computer) and the Netinstall client (the MikroTik device in Etherboot mode). The server broadcasts BOOTP requests on the local network, and devices in Etherboot mode respond to these requests, establishing a connection through which RouterOS packages are transferred. This network-boot mechanism bypasses the device’s normal boot process, allowing reinstallation even when the installed operating system is non-functional.

Devices supported by Netinstall include the entire range of MikroTik hardware, from compact home routers like the hAP series to powerful Cloud Core Router models. The same Netinstall tool works across all device types, though the specific steps for entering Etherboot mode may vary between models. The tool automatically detects the device architecture and presents only compatible RouterOS packages for installation, preventing accidental installation of incorrect software versions.

When to Use Netinstall

Netinstall should be considered when standard recovery methods have failed or when the device is completely inaccessible. Common scenarios warranting Netinstall include corrupted RouterOS installations that prevent booting, devices stuck in boot loops after failed upgrades, forgotten passwords that cannot be reset through normal means, and situations where the device’s configuration has become so corrupted that access is impossible. Before resorting to Netinstall, attempt simpler recovery methods such as booting into safe mode or using the reset configuration function.

If your device can boot and you can access it through any method (even via MAC-telnet or serial console), try less destructive recovery options first. The /system reset-configuration command can reset the device to defaults while preserving the RouterOS installation. Similarly, booting into RouterBOOT’s backup booter or using the safe mode option may allow access for troubleshooting without complete reinstallation. Netinstall should be the last resort when these options have been exhausted.

The decision to use Netinstall involves weighing the time investment against the certainty of recovery. Netinstall requires physical access to the device, a computer with the Netinstall software, and Ethernet connectivity between them. The process typically takes 5-15 minutes depending on the device and network conditions. While this represents more effort than software-based recovery, Netinstall has a near-perfect success rate for hardware-functional devices, making it the most reliable recovery method available.

Prerequisites

Required Downloads

Before beginning the Netinstall process, you need to obtain two essential components from the MikroTik download page: the Netinstall utility itself and the RouterOS main package for your device. The Netinstall utility is platform-specific, with separate versions available for Windows and Linux. The RouterOS package contains the actual operating system files that will be installed on your device.

Download the Netinstall utility from the official MikroTik download page at https://download.mikrotik.com/. Select the appropriate version for your operating system. For Windows, this is typically distributed as a ZIP archive containing the Netinstall executable. For Linux, the package is distributed as a TAR.GZ archive containing the command-line version. Both versions provide equivalent functionality, with the Linux version offering additional command-line parameters for scripted or automated installations.

RouterOS packages are organized by version number and architecture. Select a stable (recommended) or testing version based on your requirements, then choose the correct architecture for your device. Common architectures include ARM, ARM64, MIPSBE, SMIPS, and TILE. If you are unsure of your device’s architecture, you can download packages for multiple architectures—Netinstall will automatically detect and install the correct version once the device connects. For most users, selecting the Stable channel and the default architecture package is appropriate.

Network Requirements

The Netinstall process requires a direct or properly configured network connection between your computer and the MikroTik device. The device must be connected to the computer’s Ethernet port (not WiFi), as Etherboot mode uses BOOTP protocol over the wired connection. Avoid using USB Ethernet adapters if possible, as some adapters can cause link flap issues that interfere with Netinstall’s device detection.

Configure your computer with a static IP address in the appropriate subnet before running Netinstall. The specific address depends on your preference, but common choices include addresses in the 192.168.88.0/24 range ( MikroTik’s default) or the 10.0.0.0/24 range. Your computer will act as the Netinstall server, assigning IP addresses to devices that connect in Etherboot mode. Document your computer’s original network settings if you need to restore them after the installation.

If you must use a network configuration that includes switches or routers between your computer and the target device, ensure that BOOTP packets (which use the same ports as DHCP) are not blocked. Some managed switches with DHCP snooping enabled may block BOOTP requests by default; in such cases, configure the switch ports facing both the computer and the device as trusted. Alternatively, connect the device directly to your computer to eliminate any potential network equipment issues.

Windows Netinstall

Preparing Your Computer

Begin by disabling all network interfaces on your computer except the one you will use for Netinstall. This includes WiFi adapters, cellular connections, and any additional Ethernet ports. Having multiple active interfaces can cause Netinstall to listen on the wrong interface or fail to detect devices reliably. Disconnecting from all networks except the direct Ethernet connection to the target device ensures consistent behavior.

Configure a static IP address on your Ethernet interface. Open Settings and navigate to Network and Internet, then select Change adapter options. Right-click your Ethernet adapter and select Properties. In the properties window, select Internet Protocol Version 4 (TCP/IPv4) and click Properties. Choose “Use the following IP address” and enter values such as IP address 192.168.88.2, subnet mask 255.255.255.0, and leave the default gateway blank. This static configuration allows Netinstall to function predictably.

Extract the Netinstall ZIP file to a convenient location on your computer. The extraction creates a folder containing Netinstall.exe and related files. You can optionally move this folder to a permanent location or keep it in your Downloads folder. Ensure that the folder path does not contain spaces or special characters that might cause issues with command-line operations.

Running Netinstall

Launch Netinstall.exe with administrator privileges. Right-click the executable and select “Run as administrator” or right-click and choose “More” then “Run as administrator.” The application requires elevated privileges to access network interfaces and perform the installation. If Windows displays any security warnings about the application, accept them to continue.

In the Netinstall window, you will see the main interface divided into sections for Net booting, installation progress, and device list. Configure the Net booting settings by setting the Client IP address to an address in your chosen subnet (for example, 192.168.88.3) that is not already in use. The Server IP should match your computer’s static IP address. Ensure that the “Boot Server” options are configured appropriately for your network environment.

Click the “Net booting” tab and verify that the settings are correct. The Client IP address must be unique on your network and should not conflict with any existing addresses. Avoid using your computer’s own IP address for the Client IP setting, as this causes address conflicts. The Server IP should match the static IP you configured on your computer’s Ethernet interface.

Installing RouterOS

Connect your MikroTik device to your computer using an Ethernet cable plugged directly into the device’s boot port. Most MikroTik devices use ether1 as the boot port, though some devices have a dedicated BOOT port explicitly marked. Consult your device’s documentation to confirm the correct port. Do not connect any other devices between your computer and the target device, as additional network equipment can interfere with BOOTP communication.

Place the device into Etherboot mode using one of the methods described in the Etherboot section of this documentation. This typically involves holding the reset button while powering on the device or using a command if the device is still accessible. The device will display in the Netinstall window within a few seconds of entering Etherboot mode. If the device does not appear, verify the Ethernet connection, try a different Ethernet port on your computer, and confirm that the device is correctly in Etherboot mode.

Once the device appears in Netinstall, select it from the list and click “Browse” to navigate to your downloaded RouterOS packages. Select the main RouterOS package file (with .npk extension) for your device’s architecture. If you downloaded packages for multiple architectures, only the correct ones for your device will be displayed. Click “Install” to begin the installation process. A progress bar shows the transfer status.

During installation, Netinstall transfers the RouterOS packages to the device, formats the internal storage, and prepares the system for boot. This process typically takes 2-5 minutes depending on package size and network conditions. Do not interrupt the process or power off the device. When installation completes, Netinstall displays a success message and the “Reboot” button becomes active.

Post-Installation Steps

Click “Reboot” to restart the device with the newly installed RouterOS. The device will boot from its internal storage with the fresh RouterOS installation. If your device lacks a serial console, you may need to physically power cycle the device by unplugging and reconnecting the power cable. Wait for the device to complete its boot process, which typically takes 30-60 seconds.

After reboot, the device appears with default RouterOS configuration. If you had a previous configuration that you want to restore, you can import a backup file using the /system backup load command if you created one before the reinstall. Alternatively, manually reconfigure the device according to your requirements. Remember that some devices are not accessible through ether1 with the default configuration for security reasons; consult the Default Configurations documentation for details.

If you selected the “Keep old configuration” option during installation, Netinstall attempts to preserve your previous configuration. This process downloads the configuration database before reinstallation, performs the reinstallation (including formatting), and then uploads the configuration back to the device. Note that this option preserves only the RouterOS configuration database—it does not restore separate files such as User Manager databases, Dude database installations, or other stored data.

Linux Netinstall

Installing Netinstall

Download the Linux version of Netinstall from the MikroTik download page. The file follows the naming convention Netinstall-[VERSION].tar.gz, where VERSION indicates the RouterOS version compatibility. Extract the archive using the tar command with the appropriate flags for gzip compression:

tar -xzf Netinstall-[VERSION].tar.gz

This extraction creates a Netinstall-cli executable in the current directory. The executable is a command-line tool that provides all Netinstall functionality without a graphical interface. Move the executable to a permanent location such as /usr/local/bin/ for easier access, or keep it in your downloads folder for one-time use.

The Netinstall-cli tool requires root privileges to access network interfaces and perform installation. Always use sudo when running the command, or switch to root using sudo -i or su - before execution. Attempting to run Netinstall without proper privileges results in errors about missing network access or permission denied messages.

Configuration Parameters

The Linux Netinstall command accepts numerous parameters that control its behavior. Understanding these parameters allows you to customize the installation process for specific requirements. The basic syntax follows:

sudo ./Netinstall-cli [-parameters] [address/interface] routeros-[architecture]-[version].npk

The following table describes the available parameters:

Parameter	Description
-r	Resets configuration to default during reinstallation. Without this flag, the current configuration is preserved (downloaded, reinstalled, then uploaded).
-e	Applies an empty configuration after installation, erasing any existing settings.
-b	Removes any installed branding package; the branding will not be reinstalled. Without this flag, existing branding is preserved.
-m	Enables multiple device reinstallation mode. The same device is reinstalled multiple times as long as it sends BOOTP requests.
-o	Installs each device only once per Netinstall run. Subsequent requests from the same MAC address are ignored.
-f	Ignores storage size constraints. By default, Netinstall rejects packages that exceed available storage.
-c	Allows running multiple Netinstall instances simultaneously on the same computer.
-v	Enables verbose output for debugging and monitoring installation progress.
-k	Provides a license key file (.key format) to install on the device.
-s	Applies a configuration script (.rsc format) after installation. Replaces existing configuration.
—mac	Restricts installation to the specified MAC address; ignores BOOTP requests from other devices.
-i	Specifies which network interface to use for the Netinstall server.
-a	Sets the IP address to assign to the client device. Required unless using interface parameter for auto-assignment.

The package parameter specifies one or more RouterOS .npk files to install. The system package must be listed first in the parameter list. Additional packages (wireless, routing, etc.) can follow the system package. Only compatible packages for the detected device architecture are installed.

Network Setup

Before running Netinstall, configure your computer’s network interface with a static IP address. Identify the interface name using ip link show or ifconfig -a, then set the address using ifconfig or the ip command:

sudo ifconfig eth0 192.168.88.2/24

Replace eth0 with your actual interface name, which might appear as enp0s25, ens33, or similar depending on your Linux distribution. The /24 suffix specifies the subnet mask (255.255.255.0). Verify the configuration with ifconfig eth0 or ip addr show eth0.

Some systems require additional commands to bring the interface up and ensure it has a link. If the interface appears down, activate it:

sudo ip link set eth0 up

Verify link connectivity using tools like ethtool eth0 or ip link show eth0. The interface should show “UP” status and indicate a link to the connected device.

Performing Installation

With your network configured, execute Netinstall with the appropriate parameters for your installation type. The following examples demonstrate common scenarios:

Example 1: Basic installation with configuration reset:

sudo ./Netinstall-cli -r -a 192.168.88.3 routeros-mipsbe-7.14.2.npk

This command installs RouterOS 7.14.2 for MIPSBE architecture with a reset to default configuration. The client device receives IP address 192.168.88.3.

Example 2: Installation with empty configuration and branding removal:

sudo ./Netinstall-cli -e -b -i eth0 -a 192.168.88.3 routeros-arm64-7.14.2.npk wireless-7.14.2-arm64.npk

This command installs RouterOS for ARM64 architecture including the wireless package. The device receives an empty configuration and any existing branding is removed.

Example 3: Installation with configuration script:

sudo ./Netinstall-cli -s /path/to/config.rsc -a 192.168.88.3 routeros-mipsbe-7.14.2.npk

This command applies the specified configuration script after installation, replacing default settings with those from the file.

Monitor the installation output for progress and any error messages. Successful installation ends with the message “Sent reboot command,” indicating that Netinstall has completed the transfer and instructed the device to restart. The device now boots with the newly installed RouterOS.

Etherboot Mode

Understanding Etherboot

Etherboot is a special boot mode available on all MikroTik devices that enables network-based installation via Netinstall. When in Etherboot mode, the device does not load RouterOS from its internal storage. Instead, it listens for BOOTP requests from a Netinstall server and prepares to receive RouterOS packages over the network. This mode bypasses any corruption or misconfiguration in the installed RouterOS, making it the foundation of the recovery process.

The RouterBOOT bootloader manages Etherboot mode access. Most devices have two bootloaders available: the regular booter and the backup booter. The regular booter is accessed by pressing Ctrl+E during boot (via serial console) or by pressing the reset button briefly after power-on. The backup booter provides an alternative entry point if the regular booter is damaged. Both bootloaders offer Etherboot functionality.

Understanding Etherboot entry methods is essential because different situations call for different approaches. If your device can still boot and you can access it through any method, using a RouterOS command is the simplest approach. If the device cannot boot normally but you have physical access, the reset button method works for most devices. For advanced recovery scenarios, serial console access provides the most control over the boot process.

Reset Button Method

The reset button provides the most common method for entering Etherboot mode on MikroTik devices. This button, present on virtually all MikroTik hardware, initiates the Etherboot process when pressed during power-on. The exact procedure varies slightly between device models but follows a consistent pattern.

To enter Etherboot mode using the reset button, power off the device completely. Press and hold the reset button, then power on the device while continuing to hold the button. Keep the button pressed for several seconds, typically until you see activity in the Netinstall window or until the device’s LEDs indicate boot mode entry. The specific LED behavior varies by model; common indicators include the user LED blinking or remaining solid.

Release the reset button after the device indicates it has entered Etherboot mode. The device now appears in the Netinstall window on your connected computer. If the device does not appear, try holding the reset button longer, or consult your device’s documentation for model-specific instructions. Some devices require different timing or LED recognition for successful Etherboot entry.

If your device has RouterBOOT protected bootloader enabled, the reset button’s behavior changes. The protected bootloader prevents unauthorized Etherboot entry by requiring a PIN or password. Ensure you know the protected bootloader configuration before attempting recovery, as forgotten settings prevent Etherboot access entirely. The protected bootloader settings are independent of RouterOS configuration and cannot be reset without physical access to the device.

RouterOS Command Method

If your device can boot RouterOS and you can access it through any method (WinBox, SSH, Telnet, MAC-telnet, or serial console), you can initiate Etherboot mode using a RouterOS command. This method is convenient because it does not require physical button pressing and works consistently across device models.

Connect to the device and execute the following command to configure the boot device:

/system routerboard settings set boot-device=try-ethernet-once-then-nand

This setting instructs RouterBOOT to attempt booting from Etherboot on the next boot, then fall back to NAND (normal) boot if Etherboot fails. After setting this parameter, reboot the device using /system reboot or by power cycling it. On the next boot, the device enters Etherboot mode automatically.

Note that this is a one-time setting—the device attempts Etherboot only on the immediate next boot. After that boot attempt (whether successful or not), the device returns to normal boot behavior. If the Etherboot attempt fails (for example, if no Netinstall server is available), the device falls back to booting from NAND. To enter Etherboot again, either reconfigure the setting or use the reset button method.

Serial Console Method

Devices with serial console ports can enter Etherboot mode using keyboard commands during the boot process. This method provides precise control and is useful when other methods are unavailable or unreliable. Connect to the device’s serial console using a null modem cable and terminal software configured with the appropriate parameters.

The serial console parameters for most MikroTik devices are 115200 baud, 8 data bits, 1 stop bit, no parity, and flow control set to none (115200-8N1). For older RouterBOARD 230 series devices, use 9600 baud with hardware (RTS/CTS) flow control. Configure your terminal software (such as minicom, PuTTY, or screen) with these settings before connecting.

When the device powers on, watch the serial console output for the prompt to enter Etherboot mode. The message “Press Ctrl+E to enter Etherboot mode” appears during the boot process. Press and hold Ctrl+E (or the key combination for your terminal software—Ctrl+E sends the ASCII control sequence) within the 2-second window. The console displays “trying BOOTP protocol” when the device enters Etherboot mode.

With the device in Etherboot mode, it should appear in the Netinstall window on your computer. The serial console continues to display status messages showing BOOTP negotiation progress, IP address assignment, and file transfer status. This output can be valuable for troubleshooting installation issues, as it shows exactly what the device is attempting and where any failures occur.

Troubleshooting

Device Not Appearing in Netinstall

When the device does not appear in Netinstall after entering Etherboot mode, several factors may be at fault. Begin by verifying physical connections: ensure the Ethernet cable is firmly connected to both the device and your computer, try a different Ethernet port on your computer, and confirm that the cable is functioning by testing with another device if possible.

Verify that only one network interface is active on your computer. Additional active interfaces (WiFi, virtual interfaces, Bluetooth PAN) can confuse Netinstall or receive the BOOTP response instead of the interface connected to the target device. Disable all interfaces except the one directly connected to the MikroTik device.

Check your computer’s firewall and security software. Some firewall configurations block BOOTP packets or interfere with network discovery. Temporarily disable firewall software during the Netinstall process to determine if it is the cause. If the device appears after disabling the firewall, configure an exception for Netinstall rather than leaving the firewall disabled.

Confirm that the device is genuinely in Etherboot mode. If using the reset button method, observe the device’s LEDs during power-on—most devices display specific LED patterns when in Etherboot mode. If using serial console, verify that the console shows “trying BOOTP protocol” messages. Devices that appear to hang during boot or display error messages may have hardware issues requiring different troubleshooting.

Installation Failures

Installation failures can occur due to network issues, package incompatibility, or storage problems. If the progress bar does not move or Netinstall shows no status after selecting a device, try closing and reopening Netinstall, then put the device into Etherboot mode again. Persistent failures may indicate a problem with your computer or network configuration.

Verify that the RouterOS package architecture matches your device. Installing packages for the wrong architecture fails with various error messages. Check your device’s architecture by consulting the MikroTik product page or the label on the device packaging. When in doubt, download packages for multiple architectures—Netinstall only displays compatible packages after the device connects.

Some devices have limited storage capacity that may be insufficient for the selected RouterOS version. Netinstall normally checks available storage and rejects packages that exceed capacity, but the -f flag can override this check. If you use this override, the installation may fail partway through or the device may not boot correctly due to insufficient storage.

If multiple devices appear in Netinstall and you only intended to install one, use the --mac parameter (Linux) or the device filtering options (Windows) to restrict installation to the target MAC address. This prevents accidentally installing RouterOS on the wrong device.

Post-Installation Issues

Devices that fail to boot after Netinstall may have hardware problems, incorrect package installation, or corrupted boot sectors. Attempt to boot into RouterBOOT setup by pressing any key during the brief window after power-on. From the setup menu, you can select the boot device and perform basic diagnostics.

If the device boots but shows a license level lower than expected, the license was not properly preserved. Connect to the device and verify the license status with /system license print. Contact MikroTik support if the license was legitimately purchased and the license file was not transferred during reinstallation.

Configuration issues after reinstall with the “keep old configuration” option may indicate corruption in the old configuration database. The keep old configuration feature downloads the database, reformats storage, then uploads the same database. If the original database was corrupted, the corruption persists. In this case, perform a clean installation and rebuild the configuration manually or from a known-good backup.

Related Resources

Related Topics

• First Time Configuration - Setting up a MikroTik device for the first time
• Upgrading and Installation - RouterOS upgrade procedures and package management
• RouterOS License Keys - License levels and activation procedures
• Backup and Restore - Configuration backup and restoration procedures
• Default Configurations - Understanding factory default configurations

Configuration Commands

• /system routerboard settings set boot-device=try-ethernet-once-then-nand - Configure next boot to Etherboot mode
• /system reset-configuration - Reset router to factory defaults without reinstalling
• /system reboot - Reboot the router
• /system license print - Display current license information
• /file upload - Upload files to the router

Additional Resources

• Official MikroTik Downloads
• RouterBOOT Documentation
• MikroTik Forum
• Netinstall Guide Wiki