Agent skill · research science · aiskillstore
routeros-mndp
MNDP (MikroTik Neighbor Discovery Protocol) wire format, behavior, and RouterOS /ip/neighbor integration. Use when: implementing MNDP discovery, parsing MNDP packets, working with /ip/neighbor, understanding WinBox device discovery, debugging why a router doesn't appear in neighbor lists, or when the user mentions MNDP, neighbor discovery, WinBox discovery, or /ip/neighbor.
Why this skill is useful
Provides detailed knowledge on MikroTik MNDP protocol and specific packet structures that the AI wouldn't reliably generate on its own.
What it needs
About 6k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
MNDP — MikroTik Neighbor Discovery Protocol MNDP is the UDP broadcast/multicast protocol that RouterOS uses for automatic device discovery on the local network. It is the same protocol WinBox uses to find routers. Every RouterOS device participates by default. Why This Matters for Agents /ip/neighbor on RouterOS is the CLI/REST surface for MNDP results WinBox's "Neighbors" tab is an MNDP listener Any agent implementing device discovery for MikroTik equipment needs MNDP The protocol is simple enough to implement from scratch — no library needed Protocol Basics Property Value ---------- ------- Transport UDP Port 5678 IPv4 Broadcast to 255.255.255.255:5678 IPv6 Multicast to ff02::1 (all-nodes link-local) Direction Bidirectional — same port for send and receive Authentication None — read-only discovery, no credentials Scope Layer 2 broadcast domain (does not cross routers) How Discovery Works 1. Listener sends a refresh packet — a 9-byte UDP datagram to 255.255.255.255:5678 2. All RouterOS devices on the LAN reply — each sends a TLV-encoded announcement with identity, version, board, MAC, IP, uptime, etc. 3. Replies arrive asynchronously — devices respond within milliseconds to seconds depending on network conditions 4. RouterOS devices also announce periodically (~60s cycle) without being prompted — passive listening works but is slow to populate Refresh Packet (Discovery Request) A 9-byte packet that triggers immediate replies from all RouterOS devices on the broadcast domain: As raw bytes: 00 00 00 00 00 00 00 00 00 Response Packet TLV Format Each TLV (Type-Length-Value) record in the response: Byte order: TLV type and length are little-endian. Value encoding varies by type. TLV Type Reference Type Hex Name Value Format Notes ------ -------- ---------------- ------------- ------- 1 0x0001 MAC Address 6 bytes, big-endian Per-interface MAC, not chassis MAC 5 0x0005 Identity UTF-8 string Hostname — same across all interfaces 7 0x0007 Version UTF-8 string e.g. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/routeros-mndp