Did something break in IPv6 recently?

I've had IPv6 working fine for years and just noticed something odd. My router shows it is not getting a /60 prefix from the ISP and doesn't have any IPv6 addresses aside from link local...but devices on the LAN do have IPv6 addresses in the usual prefixes that I used to get from the ISP. Also, I run a script upon DHCPv6 prefix refresh on the router to update DNS, and I got the "succeeded" email the script sends when it runs, with the correct prefix. It's a RB5009 running 7.21.2.

I haven't changed IPv6 settings in months.

Here's the config. The addresses are messed up too. It should be adding ::1/64 as the router address for each vlan, but when I enter that it changes it to the ::2:0:0:1 thing, and I have no idea why. I disabled them because they don't seem to be working correctly.

/ipv6 pool
add name=ipv6-pool prefix=::/0 prefix-length=64
/ipv6 address
add address=fddc::100 advertise=no interface=wireguard1
add address=::1 disabled=yes from-pool=ipv6-pool interface=vlan-lan
add address=::2:0:0:0:1 disabled=yes from-pool=ipv6-pool interface=vlan-guest
/ipv6 dhcp-client
add add-default-route=yes custom-iana-id=0 custom-iapd-id=0 \
    default-route-tables=main interface=ATTbridge pool-name=ipv6-pool \
    prefix-hint=::/60 request=prefix script=refreshCFIPv6 use-peer-dns=no
/ipv6 nd
set [ find default=yes ] interface=vlan-lan ra-interval=30s-3m ra-lifetime=10m
add interface=vlan-guest ra-interval=30s-3m ra-lifetime=10m
/ipv6 nd prefix default
set preferred-lifetime=10m valid-lifetime=10m
/ipv6 settings
set accept-router-advertisements=yes

And the DHCPv6 client status is stuck on "searching..."

[david@RoutyMcRouterson] > /ipv6 dhcp-client/print
Columns: INTERFACE, STATUS, REQUEST
# INTERFACE  STATUS        REQUEST
0 ATTbridge  searching...  prefix 

But yet...my Windows laptop gets multiple IPv6 addresses. I don't know why it's getting them across multiple /64 prefixes, or what the first two are. Are these RAs leaking in from the ISP? Even though I have IPv6 addresses, I don't have IPv6 connectivity.

   Connection-specific DNS Suffix  . : elbonia
   IPv6 Address. . . . . . . . . . . : ::1f40:1212:8ed:c25d
   Temporary IPv6 Address. . . . . . : ::2825:c59c:37fa:da98
   IPv6 Address. . . . . . . . . . . : 2600:1700:7c50:3791:x:x:x:x
   Temporary IPv6 Address. . . . . . : 2600:1700:7c50:3791:x:x:x:x
   Temporary IPv6 Address. . . . . . : 2600:1700:7c50:3792:x:x:x:x
   IPv6 Address. . . . . . . . . . . : 2600:1700:7c50:3792:x:x:x:x
   Link-local IPv6 Address . . . . . : fe80::5f4c:e8e1:5efb:335d%18
   IPv4 Address. . . . . . . . . . . : 192.168.4.115
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : fe80::4aa9:8aff:fed0:92e3%18
                                       192.168.4.1

Anyone know what could be going on?

Update: it seems to be working sporadically. I downgraded to 7.21 and walked away, and when I returned I had the usual IPv6 addresses. But then it stopped working. I disabled and re-enabled the DHCPv6 client, and it came back up.

But there is something else odd going on. My laptop, which is on the “LAN” vlan, is getting IPV6 addresses across both prefixes for both vlans. I don’t know why. You can see it in the above snippet, too.