Can post it here?     

This is where I'm having problem ...
WAN can get both v4 & v6 once connect, but the LAN seem need to wait around 5~20mins (similar to those ASUS routers).  If lucky, may be the LAN interface can get v6 after 5~15mins of waiting, then no problem to test/visit on those v6 sites.  But later, say 1/2 hour or few hours later wake up next day, my PC can't test/visit v6 sites 
It's like now you have it then you don't 

I could be wrong, I do notice if I put all 3 interfaces (LAN/WAN/WAN6) MTU to same value (say 1480 or 1492), then high chance the LAN can get v6

at first, it is working fine..
but this few days, all ipv6 address are not working properly..

i am using one chrome extension called IPvFoo..
I can see what ip address it is trying to load for that hostname.

When I enabled ipv6, It can't get any ipv6 address, and no fall back to ipv4 address. Which cause some page not to load.. like lowyat forum..
Where else when I disable ipv6, it can load ipv4 address properly..

Did TM gives out /56 prefixes now?

Oh, just played with a Unifi Biz 100MB account, and I found out it gives out /56 prefix.

Uhh noob question here. What is the point of this ipv6 over the ipv4?

still not working leh

router shows connected ipv6

but windows pc or any phone on wifi have no ipv6 internet access

My problem is local though. TM's side still OK. Just that my devices all end up with more than 1 valid prefix, don't know which one to use and ipv6 connectivity dies.

What router are you using?

Just another update
ipv6 does now seem to work for android. before it didn't but when i checked later on it worked 

few places i check on android device

- lan ipv6, works
- wan external ipv6, works
- https://ipv6-test.com  (results show native ipv6 working, SLAAC no. Ipv6 supported yes.)
I updated ubiquiti unifi ap and so it rebooted. so i think this is why now it works properly. because i did not reboot the wireless ap earlier after having configured pfsense? that's all i can think of why it wasn't working before 
my pfsense setting is the same

- WAN, dhcpv6 (settings like anhs posted but the change is prefix /64 )
- LAN ( track interface. the change is, for the other interfaces like vlans i setup for IOT, guest wifi etc, i had to add the prefix 1,2,3 and so on. Ans did not mention any of this in his settings, but this is what was required for those like myself using vlans)

- DHCPV6 server (disabled. not using this. honestly i'm confused why he opted not to configure this. all i know is that regardless of this disabled, ipv6 still works without it)

- RA (i'm using same like ANS posted, which is Assisted)
https://forum.netgate.com/topic/100931/ra-r...-vs-unmanaged/2
under this guideline i'm not sure that my config is the best setup, but considering it works i'm content xd...
now remains to be seen if this ipv6 pfsense config can persistent without the issue some of us experienced before ^^; (that said, i did try rebooting pfsense, disconnect wan/reconnect and it was able to connect back to wan just fine without issue)
*update

further troubleshoot,

i don't know why but android ipv6 is not fully working. for example, https://ipv6test.google.com
when doing a quick check, one moment the ipv6 shows it's working. then test a minute or so later it's not working. and it's constantly fluctuating between working and not working. but when i try the same test on desktop pc (windows 11), it works fine all the time. So i'm unsure why it's like this for android, any ideas?


*update

i notice though that when enable mullvad vpn app, ipv6 will consistently work. i setup mullvad to use cloudflare dns ipv4/ipv6 so i can only think that perhaps the dns setting on pfsense is somehow not working correctly or something for android    just don't know how to fix without using my vpn app. but this issue seems restricted to android, doesn't seem to be affecting windows 11 desktop pc at all.