ok...

Only the 2000::/3 range is allowed... how am I supposed to setup a global unicast-address in a private network? Its not the purpose of a cheap TP-Link device to exist in an environment where someone actually has its own static prefix, if Id had that amount of money, I would certainly not choose TP-Link.

Ok thanks TP-Link for disabeling IPv6 for me because I cannot afford my own prefix.

  @d0ugmac1 

thank you, Im curious if thats gonna happen soon. 

But now thinking about this topic... I have two ISPs but I dont have my own prefix and even if I had my own prefix, I would need to announce it to both ISPs, which is very unlikely to ever happen in an non-enterprise environment (because which ISP will accept BGP prefixes).

So in the world of multi-WAN, non-BGP sites (which should be all of the multi-wan customers of tp-link), how should multi-WAN without NATing work in IPv6, because normally ipv6 is meant to be global-unicast. 

So tp-link would need to implement IPv6 NATing to enable local-unicast addresses, which costs a LOT of performance.

Taking all this into account, I dont think we will ever see that feature.

But at least tp-link should add this as documentation and error-message, so nobody needs to ask again, why local-unicast wont work.