Can't assign IPv6 to LAN interface

Running LEDE on a TP-Link WAP so it only has a lan interface. My network is dual stack, multiple vlans and I'm trying to assign a static ipv6 address to the wap so I can manage it over ipv6.

eth0: 2001:470:xxxx:zzzz:2/64-- mgmt network
br1 (bridging eth0.44 + 1 SSID): -- lan users
br2 (eth0.55 + 1 SSID): - guests
br3 (eth0.66 + 1 SSID): - iot

Eventually I'd want to add an ipv6 address to the other bridges, but for now just trying to get it working on eth0.

I can access the wap fine on all ipv4 addresses, can't via the ipv6 address on eth0. From the web ui, I assigned a static ipv6 address to eth0 and on the web interface overview page it shows the ipv6 address as being assigned to eth0. Try to ping, no luck.

I then ssh into the wap and do an ifconfig eth0 and it's not showing the ipv6 address being assigned:

    root@LEDE:~# ifconfig eth0
    eth0      Link encap:Ethernet  HWaddr 60:E3:27:F5:8E:4B  
              inet addr:  Bcast:  Mask:
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:20284 errors:0 dropped:0 overruns:0 frame:0
              TX packets:14858 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:8152487 (7.7 MiB)  TX bytes:4547786 (4.3 MiB)

Feel like I'm missing something, but not quite sure what it is?

Help appreciated.

This IP appears to be for an tunnel (not for eth0)...where are the configs for your WAN and tunnel?

Yup, an HE tunnel it is. I have an HE /48 routed to my pfsense box and the plan is this wap with LEDE will have static addresses from 4 different /64s assigned to it: 1 /64 address for the the mgmt network above and then (eventually) a separate /64 address for each ssid (lan, guest, iot vlans). Clients connecting to the ssids are already getting addresses from the /64, I've just been trying to setup ipv6 addresses on the wap itself so I can manage lede over ipv6.

Again, this device I'm running lede on is just a wap and has only one interface, eth0 (plus vlan interfaces on top of eth0).

Although after rebooting lede, eth0 seems to have picked up its assigned static ipv6 address and as of now things seems to be working as expected.