Routeros Netinstall

{
  "schema_version": "2.0",
  "meta": {
    "generated_at": "2026-04-16T21:09:52.735Z",
    "slug": "tikoci-routeros-netinstall",
    "source_url": "https://github.com/tikoci/routeros-skills/tree/main/routeros-netinstall",
    "source_ref": "main",
    "model": "claude",
    "analysis_version": "3.0.0",
    "source_type": "community",
    "content_hash": "425ead1393cecf05aa291e45f14cdc355c54d792378d8dcfeb97a3849fc151da",
    "tree_hash": "ab7b52a183205f83954dca1424d0271b75203cbdb7dd9e9fccc1a844895d033d"
  },
  "skill": {
    "name": "routeros-netinstall",
    "description": "MikroTik netinstall-cli for automated RouterOS device flashing. Use when: automating netinstall, writing scripts that invoke netinstall-cli, building netinstall tooling, understanding etherboot/BOOTP/TFTP protocols, working with RouterOS package files (.npk), using modescript or configure script, or when the user mentions netinstall, etherboot, or device flashing.",
    "summary": "Reference documentation and automation patterns for MikroTik RouterOS netinstall device flashing.",
    "icon": "📦",
    "version": "1.1.0",
    "author": "tikoci",
    "license": "MIT",
    "category": "devops",
    "tags": [
      "mikrotik",
      "routeros",
      "netinstall",
      "device-flashing",
      "network-administration"
    ],
    "supported_tools": [
      "claude",
      "codex",
      "claude-code"
    ],
    "risk_factors": []
  },
  "security_audit": {
    "risk_level": "safe",
    "is_blocked": false,
    "safe_to_publish": true,
    "summary": "This skill is a documentation-only SKILL.md file (252 lines) describing MikroTik RouterOS netinstall-cli usage. The static analyzer flagged 124 patterns, but all are false positives from misinterpreting markdown formatting. Backtick-enclosed text (e.g., `netinstall-cli`) is markdown inline code formatting, not Ruby/shell execution. Sudo references, shell command substitution examples, and network URLs appear in documented code examples and reference links. The file contains no executable code, no secrets, and no malicious patterns. Safe for publication.",
    "risk_factor_evidence": [],
    "critical_findings": [],
    "high_findings": [],
    "medium_findings": [],
    "low_findings": [],
    "dangerous_patterns": [],
    "files_scanned": 1,
    "total_lines": 252,
    "audit_model": "claude",
    "audited_at": "2026-04-16T21:09:52.735Z",
    "risk_factors": []
  },
  "content": {
    "user_title": "Install and manage RouterOS devices with netinstall",
    "value_statement": "MikroTik RouterOS device flashing requires understanding BOOTP, TFTP, package management, and scripting. This skill provides complete netinstall-cli reference documentation with automation patterns for single-device and multi-device installations.",
    "seo_keywords": [
      "MikroTik RouterOS",
      "netinstall-cli",
      "device flashing",
      "etherboot",
      "BOOTP TFTP",
      "RouterOS packages",
      "Claude Code",
      "Codex",
      "network automation",
      "modescript"
    ],
    "actual_capabilities": [
      "Explain netinstall-cli flags, syntax, and usage for RouterOS device installation",
      "Document etherboot entry methods including reset button, serial console, and CLI approaches",
      "Describe configure script versus mode script differences and use cases",
      "Guide RouterOS package file (.npk) selection, download URLs, and architecture naming",
      "Provide automation patterns for single-device, multi-device, and scripted netinstall workflows",
      "Explain cross-platform execution requirements including QEMU emulation on ARM hosts"
    ],
    "limitations": [
      "This skill provides documentation only. It does not execute netinstall commands or interact with devices.",
      "Actual netinstall operations require physical hardware access, root privileges, and direct Layer 2 connectivity.",
      "Package download URLs and version channels reference external MikroTik servers managed outside this skill.",
      "Cross-platform emulation (QEMU on ARM, macOS) requires separate system configuration not covered in depth."
    ],
    "use_cases": [
      {
        "title": "Network administrator deploying RouterOS at scale",
        "description": "Use netinstall automation patterns to flash multiple RouterOS devices simultaneously in a lab or production environment. Reference the multi-device install service loop with -m -o flags for efficient batch provisioning.",
        "target_user": "Network administrator"
      },
      {
        "title": "DevOps engineer building RouterOS CI/CD pipelines",
        "description": "Integrate netinstall-cli into containerized build pipelines for automated RouterOS testing. Reference the containerized netinstall pattern with VETH networking and environment variable configuration.",
        "target_user": "DevOps engineer"
      },
      {
        "title": "Technician recovering bricked RouterOS devices",
        "description": "Follow etherboot entry procedures and single-device install steps to recover devices that failed firmware updates or have corrupted configurations. Use the configure script pattern for customized defaults.",
        "target_user": "IT technician"
      }
    ],
    "prompt_templates": [
      {
        "title": "Basic netinstall command construction",
        "prompt": "I need to install RouterOS 7.22 on an ARM64 MikroTik device. Build the netinstall-cli command with reinstall defaults and discard branding package on interface eth0.",
        "scenario": "A user needs a basic single-device install command for a standard RouterOS deployment."
      },
      {
        "title": "Modescript for device-mode configuration",
        "prompt": "Write a modescript that enables advanced mode with container and zerotier support, then show the netinstall-cli command to apply it on first boot.",
        "scenario": "A user wants to configure device-mode features automatically during netinstall without manual power-cycle confirmation."
      },
      {
        "title": "Cross-platform netinstall on ARM host",
        "prompt": "I have an ARM64 Linux server and need to run netinstall-cli. Explain the QEMU user-mode setup and show how to auto-detect the correct QEMU binary for transparent execution.",
        "scenario": "A user runs netinstall-cli on a non-x86 host and needs emulation configuration guidance."
      },
      {
        "title": "Containerized netinstall service on RouterOS",
        "prompt": "Set up netinstall-cli as a RouterOS container that automatically installs RouterOS on devices connecting to the LAN. Configure the container with VETH networking, arm64 architecture, stable channel, and container plus wifi packages.",
        "scenario": "A user wants their RouterOS router to serve as a self-provisioning netinstall server for other devices on the network."
      }
    ],
    "output_examples": [
      {
        "input": "Install RouterOS 7.22 with container and WiFi packages on an ARM64 device via eth0.",
        "output": [
          "Run: sudo netinstall-cli -r -b -i eth0 routeros-7.22-arm64.npk container-7.22-arm64.npk wifi-qcom-7.22-arm64.npk",
          "Ensure the device is in etherboot mode (hold reset button while powering on until it appears in netinstall).",
          "The system package (routeros-*.npk) must be listed first in the command."
        ]
      },
      {
        "input": "How do I enter etherboot mode using the RouterOS CLI?",
        "output": [
          "Run this command in RouterOS CLI: /system/routerboard/settings/set boot-device=try-ethernet-once-then-nand",
          "Then reboot the device. It will attempt ethernet boot once before falling back to NAND.",
          "After netinstall completes, the boot device setting returns to normal."
        ]
      }
    ],
    "best_practices": [
      "Always list the system package (routeros-VER-ARCH.npk) first in the netinstall-cli package list to ensure correct installation order.",
      "Use a dedicated network interface or switch with no other DHCP sources to avoid BOOTP conflicts during etherboot device discovery.",
      "Apply DNS retry logic (5 attempts with 2-second delays) when running netinstall in containers at boot time, as DNS may not be immediately available."
    ],
    "anti_patterns": [
      "Do not combine -r (reinstall with defaults) and -e (reinstall with empty config) flags. They are mutually exclusive and produce undefined behavior.",
      "Avoid using USB Ethernet adapters directly between host and device. Link flaps from USB adapters can prevent device detection. Use a switch as an intermediary.",
      "Do not run netinstall-cli on networks with active DHCP servers without isolation. BOOTP uses the same ports as DHCP and will cause address conflicts."
    ],
    "faq": [
      {
        "question": "What is the difference between netinstall and netinstall-cli?",
        "answer": "Netinstall is the Windows GUI application. Netinstall-cli is the Linux command-line tool distributed as an x86 ELF binary. Both perform the same RouterOS installation function over Ethernet using BOOTP and TFTP protocols."
      },
      {
        "question": "Why does netinstall-cli require root or sudo privileges?",
        "answer": "Netinstall-cli uses BOOTP on port 67/68 and TFTP on port 69. These are privileged ports below 1024 that require root access on Linux systems. The tool also performs low-level network operations for device discovery."
      },
      {
        "question": "Can I run netinstall-cli on a Mac or ARM Linux machine?",
        "answer": "On x86_64 Linux, netinstall-cli runs natively. On ARM/ARM64 Linux, use QEMU user-mode emulation with qemu-i386-static or qemu-i386. On macOS, a full QEMU virtual machine with bridged networking is required because QEMU user-mode emulation is Linux-only."
      },
      {
        "question": "What is the difference between a configure script and a mode script?",
        "answer": "A configure script (-s flag) runs after default config is applied and persists across upgrades until re-netinstalled. A mode script (-sm flag, RouterOS 7.22+) runs once on first boot before other scripts and is auto-deleted after execution. Mode scripts are ideal for initial device-mode setup."
      },
      {
        "question": "How do I enter etherboot mode on a MikroTik device?",
        "answer": "Four methods exist: hold the reset button while powering on until the device appears in netinstall; press Ctrl+E during boot via serial console; set boot-device to try-ethernet-once-then-nand via RouterOS CLI and reboot; or use the protected bootloader method if previously configured."
      },
      {
        "question": "Where do I download RouterOS package files (.npk)?",
        "answer": "Download packages from download.mikrotik.com using the pattern: https://download.mikrotik.com/routeros/VERSION/routeros-VERSION-ARCH.npk. You can also extract individual packages from the all_packages-ARCH-VERSION.zip archive for your architecture."
      }
    ]
  },
  "file_structure": [
    {
      "name": "SKILL.md",
      "type": "file",
      "path": "SKILL.md",
      "lines": 252
    }
  ]
}