IPv6 on BT with 380.66 Beta 5 on RT-N66U

[de carabas]

I posted recently that BT wasn't giving me an IPv6 address. That sorted itself in the last couple of weeks and now my router is telling me it's got addresses. The problem is that although the setup is correct nothing is routing. IPv4 works fine.
Test-ipv6.com and ipv6-test.com both give me complete fails on v6

I've posted on the BT community forum on this as I thought it might be BT issue as IPv6 work for other people with BT on this Router but no harm in asking for opinion here given some of the symptoms.

I've also tried with stock firmware which behaves the same, so I don't think it's Merlin specific issue, but I wonder if there's some way to sort using this great firmware?

Router and LAN clients are being given addresses. Pings to IPv6 addresses from LAN clients fail with timeouts or unreachable. Pings from the router (ping6 to google.com from CLI) work fine. Trace route back to my address fail in BT's network. Traceroute from my desktop Win10 pc gets to broadband.bt.com [2a00:23c5:7604:4200::1] and then stops.

I'm no network expert and even less than that in IPv6. Any thoughts to add to what we've tried so far would be much appreciated.

 

[RMerlin]

Try a complete network restart, IPv6 support on LAN can still be quirky.

1) Turn off modem, router and computers
2) Turn on modem, let it sync
3) Turn on router, let it connect
4) Turn on computers

This way, you will ensure that IPv6 delegation gets completely refreshed throughout the whole LAN.

 

[de carabas]

Thanks for the suggestion. I tried it, allowing several minutes between steps (and watching for lights to settle etc) but no change.

 

[RMerlin]

Then welcome to the world of IPv6, where home stuff rarely works as expected...

 

[de carabas]

Then welcome to the world of IPv6, where home stuff rarely works as expected...

Yeah, that's what I was hoping you wouldn't say
As the issue with being assigned an IP address magically sorted itself maybe this will as well. I will not hold my breath though.

 

[de carabas]

I just wanted to post for completeness in case anyone else sees something similar.
In the last couple of days a mod on the BT community forum responded asking for details from the several of us with the same issue (all in one geographical area) and escalated it somewhere within BT. Everything now works. Whatever the engineer kicked did the trick and my AC-3200 (yes I upgraded) works perfectly.
Moral of the story- keep shouting at your ISP and one day they might listen.