pfSense

After an IPv6 prefix and IP change on the WAN interface the old deprecated IPv6 address is shown on Dashboard->Interfaces and Status->Interfaces.

Seems like the IP and prefix change is not detected and client devices loose IPv6 connectivity. Additional bugs might be involved in the E2E IPv6 management.
I will post additional issues.

vtnet0 is the WAN interface.
ifconfig vtnet0 | grep 2003
inet6 2003:e2:8719:d000:11:32ff:fe20:4119 prefixlen 64 deprecated autoconf pltime 0 vltime 7197
inet6 2003:e2:8714:3800:11:32ff:fe20:4119 prefixlen 64 autoconf pltime 1798 vltime 7200

Old IP: 2003:e2:8719:d000:11:32ff:fe20:4119
New IP: 2003:e2:8714:3800:11:32ff:fe20:4119

Old IP is shown in the GUI.

Background: I’m running a CARP HA Cluster for IPv4 on pfSense Plus 24.11. Adding IPv6 to the cluster node(s) resulted in an unstable cluster. I’m testing IPv6 now in a VM running pfSense 2.7.2.
Scenario: IPv6 with dynamic IPv6 prefix advertised by upstream router via DCHPv6 to WAN Interface.
WAN IPv6 Configuration Type: DHCP6
DHCPv6 Prefix Delegation size: 61
Send IPv6 prefix hint: yes
Request only an IPv6 prefix: no

Clients are configured "unmanaged" (Stateless Address Auto-Configuration (SLAAC))

Steps to reproduce:
Initiate a IPv6 prefix change on the upstream router.

Steps to resolve / work around:
Manual workaround to show the correct IPv6 address in the GUI:
Remove the depreciated IPv6 address on CLI.
ifconfig vtnet0 inet6 2003:e2:8719:d000:11:32ff:fe20:4119/64 delete