What problem does it solve? After a CHR virtual router is reset, restored, netinstalled, or recreated in Hyper-V, it no longer matches the state the tik4net integration test suite assumes — wrong IP/MAC/identity, missing packages, no certificates, disabled services, and drifting clocks all cause confusing test failures. This Skill walks through re-provisioning the router end to end, verifying every step against the live device. ## Core Features & Use Cases - Discovery and coordinate reconciliation: Runs an MNDP broadcast scan to find MikroTik devices on the segment, lets the user confirm which one is the test box, and syncs host, MAC, and identity into tik4net.integrationtests/App.config. - Full router provisioning: Installs the complete RouterOS package set via FTP upload and reboot, configures NTP and timezone, enables all required services (api, api-ssl, www, www-ssl, telnet, ssh, winbox, ftp, discover), and creates self-signed CA/server certificates for the SSL transports. - Verification and documentation hygiene: Creates a recovery admin account, runs an 11-transport smoke matrix (Api, ApiSsl, Rest, RestSsl, Telnet, Ssh, MacTelnet, WinBox variants), and reconciles the RouterOS version promised in README and the wiki with the live router. - Use Case: After recreating the CHR VM in Hyper-V, run this Skill to discover the router, update App.config, install all 12 packages, set up certificates, and confirm all 11 transports connect before handing off to the test suite. ## Quick Start Re-initialize my CHR test router — it was just reset to defaults, so discover it on the network, update App.config, and bring it up to the state the tik4net integration suite expects.
