routeros-mndp

Solid

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.

API & Backend 40 stars 9 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
54
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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 small UDP datagram to 255.255.255.255:5678 (MAC-Telnet sends a minimal 4-byte zeroed header; a 9-byte form also works — see below) 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 prompte...

Details

Author
tikoci
Repository
tikoci/routeros-skills
Created
4 months ago
Last Updated
1 weeks ago
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

API & Backend Solid

routeros-mac-telnet

MAC-Telnet protocol (MikroTik Layer-2 terminal/exec over UDP 20561) wire format, session handshake, and MD5 + MTWEI (EC-SRP) authentication. Use when: implementing or debugging a MAC-Telnet client/server, reaching a RouterOS device by MAC address without IP, parsing MAC-Telnet packets, understanding the WinBox-style L2 terminal, deciding between classic MD5 and modern MTWEI auth, or when the user mentions MAC-Telnet, mactelnet, mactelnetd, port 20561, or MTWEI/EC-SRP RouterOS login.

40 Updated 1 weeks ago
tikoci
API & Backend Solid

routeros-fundamentals

RouterOS v7 domain knowledge for AI agents. Use when: working with MikroTik RouterOS, writing RouterOS CLI/script commands, calling RouterOS REST API, debugging why a Linux command fails on RouterOS, or when the user mentions MikroTik, RouterOS, CHR, or /ip /system /interface paths. Scope: RouterOS 7.x (long-term and newer) only — v6 is NOT covered and accuracy for v6 problems will be low.

40 Updated 1 weeks ago
tikoci
API & Backend Solid

routeros-sniffer

RouterOS packet capture and TZSP streaming for protocol debugging. Use when: capturing packets on RouterOS, setting up /tool/sniffer, streaming live traffic via TZSP, using firewall mangle action=sniff-tzsp, debugging network protocols on MikroTik, receiving TZSP with Wireshark or tshark, saving pcap files from RouterOS, or when the user mentions packet sniffer, TZSP, sniff-tzsp, /tool/sniffer, or packet capture on RouterOS.

40 Updated 1 weeks ago
tikoci