IPv6 device addresses: brackets, opt-in IPv6 network (v0.24.43)
#178. Two separate problems:
- The Add/Edit device forms only unwrapped [2001:db8::1] when a port
followed, so a plain bracketed address failed validation. Brackets are
now dropped either way (addressFieldValue), and CSV import accepts them. - The backend container had no IPv6, so IPv6 devices were unreachable on a
default install. The backend now joins a separate device-ipv6 network
whose IPv6 is switched by ENABLE_IPV6 in .env, off by default.
app-network is left alone: enabling IPv6 on it in place reattached the
running containers without their service names and the backend lost
postgres. Off by default because Docker enabling IPv6 forwarding can make
a SLAAC host stop accepting router advertisements (needs accept_ra=2).
Docs cover host requirements and down/up to switch it.
Also: nodemailer 10.0.12 and engine.io 6.6.11 for GHSA-v53p-9fqp-m79j and
GHSA-2gc4-cqfq-p2gv (both high, published today).
Tested locally: upgrade from the current network with a plain up -d (only
backend recreated, service names intact), enable/disable via down/up, and
the three address forms in the browser.
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.24.43-betaghcr.io/2gt-media-group-llc/mikrotik-manager-nginx:0.24.43-beta
Documentation: https://2gt-media-group-llc.github.io/mikrotik-manager/