First, I am not very experienced with IPv6 but I am very experienced with IPv4. I use a cable modem to get internet access and have been using UTM for a while now. I am not a n00b other than with IPv6.
I receive a public IPv6 address on WAN when IPv6 is enabled. I also receive a /64 PD. Everything seems to work ok in that regard. I have set up my DNS server with an IPv6 address [ipv6-pd::100] and a clients with [ipv6-pd::***] assigned statically as well as [ipv6-pd::1] for the UTM interface. All machine can talk to each other and all machines can talk to the UTM just fine. I can browse IPv6 addresses with the clients (Centos server updates, Windows 8.1 desktop) I have tested and get the correct information reported back from ipquail.com and whatnot. It all seemed to be working fine.
However, I have another client, my son's gaming computer (Windows 8.1), that was crapping out all over the place. He mentioned that he could not get signed into steam. Odd, but whatever. I checked logs, nothing at all was being blocked or dropped. Everything in the logs showed IPv4 addresses. I verified that IPv4 was preferred over IPv6. I then removed the IPv6 gateway, and it still did not work. I ended up having to disable IPv6 on the UTM completely, then the steam client was finally happy again.
I ran into a similar situation with his Xbox One. With IPv6 enabled on the UTM, the NAT settings on the XBOne were grumpy. Again, disabling IPv6 makes it happy again.
All machines can still talk to each other (other than the UTM of course) with IPv6 enabled.
I know this is a shot in the dark, but anyone have any good troubleshooting tips by chance? I have seen references that IPv6 may not be fully baked in the UTM - could that be causing issues? I fully own that I am probably the issue here [:)]. Any help would be appreciated. TIA!
This thread was automatically locked due to age.