Find the manager's WireGuard tunnel over IPv6; read 7.24 connection ports (v0.35.1)
#205: an IPv6-only management tunnel wasn't recognised, so it stayed
editable. Tunnel detection only read /ip/address, /ip/route and the IPv4
connection table. It now reads the IPv6 ones too, compares addresses
canonically, and looks for the address the API connection actually
reached, so a device added by hostname is found as well.
RouterOS 7.24 gives connection-table entries separate src-port/dst-port
fields and a bare address (IPv4 and IPv6). The parser expected
"address:port", so on 7.24 the manager never saw its own connection:
Change Guard fell back to the default gateway and the WireGuard page
couldn't single out the manager's peer. Both forms are read now.
Tested on a CRS309 (7.24.5) with an IPv6-only WireGuard interface:
found by its address and by an IPv6 route back to the manager; the
IPv4-managed device now reports the manager's address. Switch restored.
Docs: change-guard.md (The manager's WireGuard tunnel).
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
Container images (published once CI passes):
ghcr.io/2gt-media-group-llc/mikrotik-manager-backend:0.35.1-betaghcr.io/2gt-media-group-llc/mikrotik-manager-nginx:0.35.1-beta
Documentation: https://2gt-media-group-llc.github.io/mikrotik-manager/