Sure it's possible, but I don't think the Internet is much fun when 99% of it is inaccessible...

Start troubleshooting by pinging your router. It's the fe80::xxxx IP listed in "IPv6 Default Gateway" ... make sure you include the %38 at the end.

Did that work? If it did, run a tracert -6 google.com and paste the results here.

From what I see, I think it's a problem on TM's side. Try calling their hotline. Their customer support needs some practice resolving IPv6 problems after all

???????

You don't need port forwarding. Every computer on your IPv6-enabled LAN will get a publically-routable IP address.

This is not a place for you to troll. If you can't post properly, then don't post at all.

No they don't. The IPs that TM serves out belong to TM (2001:e68::::/32)

kupang I think you're very confused. IPv6 is nothing like IPv4 when it comes to LAN addressing so it's time to relearn this

1) You do not need to specify "private LAN IPs", because it's auto-generated by the operating system.
2) All your PCs on the LAN will get a public IP.
3) You do not necessarily need DHCPv6 to assign addresses, provided that the router announces its public IPv6 prefix using SLAAC.

I haven't used that router before so I can't advise what settings you should put. I have a feeling that it's easier to reset it to factory defaults and see if it works out of the box.

If you have SLAAC on the LAN side, you don't need DHCPv6.

khoodennis I merged your topic into this pre-existing one.

It could be a problem at TM.

For my office connection, we could get our static prefix assigned using DHCPv6-PD with our Mikrotik for a few weeks... and it stopped after that. Like you, I can get a SLAAC prefix only. I haven't gotten around to calling in to raise a fault.

So, just saying that it's not necessarily a client software problem.

Unless you're running a mailserver, it's not really important and you can live with it. TM doesn't have reverse DNS setup for its IPv4 addresses so I doubt that they would bother for IPv6.

Looks like it is delegating the address, but "IPv6 default gateway" is blank - that's what you should troubleshoot I think.

Now that I've switched to Maxis, I depend on you guys to be my eyes and ears on whether the forum is working over IPv6

They're extending "no quota limit" indefinitely, but they do throttle speeds without warning.

TM and our hosting provider Ipserverone aren't peering IPv6 at MyIX.

Well Maxis provides more bandwidth at the same price...

I used an MTU of 1492 just fine... with all sorts of devices.

I suspect that the problem that some of you face is broken residential gateways that don't clamp MSS to MTU correctly. I think it's best to avoid MSS clamping, it's a hack anyway.

If your RG lets you set the MTU in Route Advertisment messages, try that first. Then your devices on the LAN will natively use an MTU of 1492 and work end-to-end without any clamping.

These days, I prefer using Mikrotik over a pfSense box. It's really capable and comes cheap.

Sounds like you are not bridging. Did you connect the TP-Link's WAN or LAN port to the D-Link?