Skip to content

Release v0.15.0

Latest

Choose a tag to compare

@github-actions github-actions released this 16 Nov 08:42

Release Notes 0.15.0

Released: 2026-11-16

This release is about IPv6. Clients and devices now carry every IPv6 address the controller reports, and you can search and look them up by any of those addresses. Networks show their actual IPv6 setup, with the delegated prefix read from the gateway. IPv6 can now be turned on from the CLI and the TUI, where before it could only be turned off. Several fixes correct IPv6 data that earlier releases read from the wrong place.

🌟 Highlights

✨ Every IPv6 Address on Clients and Devices

Clients and devices expose a new ipv6_addresses list, sorted widest reach first: global, then unique local (fc00::/7), then link-local (fe80::/10). The order comes from the new Ipv6Scope type in crates/unifly-api/src/model/address.rs. TUI detail panels show the first global and first unique local address, plus a count of the rest. A client with no IPv4 address now shows its IPv6 address in lists instead of an empty column.

🔍 Look Up and Search by IPv6

clients get and devices get accept any of a host's IPv6 addresses as the identifier. Search on the Clients, Devices, and WiFi screens matches any address. A full IPv6 address is compared by value, so 2001:0db8:0:0:0:0:0:1 finds 2001:db8::1, and a partial address still matches as text (crates/unifly/src/tui/search.rs). When an event message contains an IPv6 address, the Events detail now names the client or device behind it.

🌐 Networks Show Their Real IPv6 Setup

For a prefix-delegation network, the prefix it serves now comes from the gateway, which is the only place the controller reports what the WAN was delegated (controller/refresh/prefixes.rs). The TUI network detail and networks get now show:

  • the IPv6 mode
  • aliases such as a ULA
  • SLAAC, and DHCPv6 with its range
  • router advertisement priority
  • IPv6 DNS servers

networks list gains an IPv6 column. In the TUI, a network with no address assignment or no router advertisement shows a warning, since hosts there get no address or no default route.

⚙️ Turn IPv6 On, Not Only Off

unifly networks update <ID|NAME> --ipv6 true and the TUI network editor can now enable IPv6 on a network that has none. They apply the same defaults as the controller's own form:

  • a prefix delegated from the WAN the site's other IPv6 networks already use (if none do, the first WAN listed)
  • addresses handed out by SLAAC
  • router advertisements on, at high priority

--ipv6 false deletes the network's IPv6 settings.

🖥️ CLI

  • New --ipv6 <true|false> flag on networks update (crates/unifly/src/cli/args/networks.rs).
  • networks list adds an IPv6 prefix column. A prefix-delegation network reads - until its WAN has a prefix.
  • networks get shows IPv6 mode, prefix, aliases, SLAAC and DHCPv6, RA priority, and IPv6 DNS servers.
  • clients get and devices get resolve hosts by any of their IPv6 addresses (cli/commands/util/lookup.rs).
  • For file payloads, ipv6_enabled: true creates the default setup described above. On a network that already has IPv6, it changes nothing.

📺 TUI

  • Client and device detail panels list the IPv4 address, the first global and unique local IPv6 addresses, and a count of any others.
  • The Networks form offers IPv6 on gateway-managed networks. Turning it on makes the confirmation say where the prefix comes from. Turning it off says the settings will be deleted.
  • Clients, Devices, and WiFi search match IPv6 addresses by value or by fragment.
  • Events detail names the client or device behind an IPv6 address in a message.

🐛 Fixes

  • wan_ipv6 on non-gateway devices: every device reported its own LAN address as wan_ipv6, and a device with no WAN fell back to it. wan_ipv6 is now set on gateways only, from their WAN.
  • Network IPv6 prefix and DHCPv6: the prefix showed the network's unique local alias, and DHCPv6 always read off. Both values came from fields the Network 11 API does not have. The prefix now comes from the gateway, aliases are listed as aliases, and DHCPv6 reads on when the address assignment carries a DHCP configuration.
  • Redacted screenshots: every IPv6 address was replaced with the same stand-in, so two hosts could appear to share an address, and IPv6 in a client's or device's ip was not redacted at all. Each address now gets its own stand-in of the same reach. IPv6 is also redacted when only MACs are hidden, since a SLAAC address spells out its MAC (crates/unifly/src/sanitizer.rs).
  • Hybrid merge for IPv6-only clients: a client with no IPv4 address picked up nothing from the Session API records, because the merge matched only by IPv4. The merge in controller::refresh::merge now matches by MAC first and falls back to IPv4. New tests cover this in refresh/merge/tests.rs.

🔧 Internals

  • New Ipv6Scope enum and ipv6_in_scope helper in unifly-api classify and order addresses by reach.
  • New refresh step controller/refresh/prefixes.rs reads delegated prefixes from the gateway and attaches them to networks, with dedicated tests.
  • convert/network.rs, convert/client.rs, and convert/device.rs parse the IPv6 fields Network 11 reports.
  • The demo fleet (demo/fleet.rs, demo/fleet/devices.rs) now produces IPv6 addresses and prefix-delegation networks for demo mode.
  • Docs updated: docs/content/reference/cli.md, docs/content/reference/tui.md, crates/unifly/skill/commands.md, and AGENTS.md.

⚠️ Behavior Changes

  • wan_ipv6 is gateway-only. JSON output for switches and access points no longer includes their LAN address under wan_ipv6. To get a non-gateway device's IPv6 addresses, read ipv6_addresses instead.
  • ipv6_enabled: true no longer fails on a network without IPv6. It now creates a prefix-delegation and SLAAC setup. If a script relied on the old refusal, add your own check.
  • IPv6 prefix values change. For prefix-delegation networks, the prefix shown is now the one the gateway carved from its WAN delegation, not the ULA alias. ULAs now appear under aliases.

📝 Upgrade Notes

  • If any tooling parses wan_ipv6 from device output, switch it to ipv6_addresses for anything other than gateways.
  • A static IPv6 prefix, DHCPv6, or a WAN other than the default still has to be configured in the controller console. Update payloads have no ipv6Configuration field, so a file cannot carry one.
  • Regenerate any redacted screenshots made with earlier versions if they contain IPv6 addresses. Older redaction could leave addresses exposed or merge distinct hosts.