Dashboard: LAN Information widget shows the link-local IPv6 (fe80::) when the LAN interface has no global IPv6.

[kateatlinksys]

Reproduce steps:

1. Login to Linksys Now.
2. Go to Dashboard / Home.
3. Look at the "LAN Information" widget → IPV6 field.

Actual result:
The IPV6 field shows the link-local address fe80::7612:13ff:fe21:5394 (scope link).
Backend (serial console, ip -6 addr) confirms the LAN bridge interface br-lan currently holds only a link-local address — no global/ULA IPv6 is assigned:
13: br-lan ... inet6 fe80::7612:13ff:fe21:5394/64 scope link

Expected result:
When the LAN interface has no global IPv6 address, the field should show - / empty (consistent with how the DNS field renders when unavailable), not the link-local fe80:: address.
(If the LAN later receives a global/ULA IPv6 prefix, the widget should display that global address.)

Env.: M60DU-EU / Pinnacle 2.0 FW 1.2.2.26062820 / Linksys Now 2.5.0.700525

Log:
GUI_dashaoard_ipv6address_error_0714.txt

Screenshot:

[AustinChangLinksys]

🔍 Automated investigation (preliminary triage)

Line: 2.x / USP (TR-369)
Root cause (UI defect, backend data is correct):

• The LAN Information widget renders the LAN interface's IPv6 address without checking IPAddressStatus. The backend explicitly marks the only LAN IPv6 entry as IPAddressStatus: "Invalid" (an auto-configured link-local fe80::), but the UI still displays it.
• Per the report, when the LAN has no valid global IPv6 the field should render - / empty (consistent with the DNS field), not the link-local address.

Evidence (from attached log.txt):

1. Backend returns the LAN (Interface.1) IPv6 entry flagged as Invalid, link-local, auto-configured:

#12 GET ← (854ms)
  "Device.IP.Interface.1.IPv6Address.1.IPAddressStatus": "Invalid",
  "Device.IP.Interface.1.IPv6Address.1.Prefix": "",
  "Device.IP.Interface.1.IPv6Address.1.Origin": "AutoConfigured",
  "Device.IP.Interface.1.IPv6Address.1.IPAddress": "fe80::7612:13ff:fe21:5394",
  "Device.IP.Interface.1.IPv6Address.1.Status": "Enabled"

2. Code path confirmed on dev-2.5.0 — the LAN data service keeps addresses filtering only on empty string, ignoring IPAddressStatus and scope:

// lib/page/local_network/services/usp_lan_data_service.dart
final instances = resp.getInstances('Device.IP.Interface.1.IPv6Address.');
return instances
    .map((i) => i.getString('IPAddress'))
    .where((ip) => ip.isNotEmpty)   // ignores IPAddressStatus == "Invalid" and scope
    .toList();

3. The card then blindly renders the first element:

// lib/page/local_network/cards/usp_lan_info_card.dart
if (info.ipv6Addresses.isNotEmpty)
  ... value: info.ipv6Addresses.first,   // the "Invalid" fe80:: link-local

Suggested direction (not a fix commitment): skip entries whose IPAddressStatus != "Valid" (and/or link-local fe80::/10 scope); when none remain, render - / empty like the DNS field.

Confidence: High — backend response confirms IPAddressStatus: "Invalid" for the sole LAN IPv6; code path on dev-2.5.0 confirms UI ignores the status flag and renders .first.

---

Auto-generated triage by Austin's tooling, pending Austin's review. Not a fix commitment.