#ripe86
#ipv6
#tutorial
#ipv6basics
#ipv6only
#ipv6transition
#dualstack
#uptodate
#nat64
#464xlat
#dslite
#video
https://ripe86.ripe.net/archives/video/993/
#pdf
https://ripe86.ripe.net/presentations/33-RIPE86-IPv6-Tutorial.pdf

#Question: How is OS #464xlat support (especially in #FOSS) these days?

@lamp
With #464xlat IPv4 literals would work. But clat (the second part of 464xlat) depends on you/your device.

@doachs i've put the dns64 on my computer and haven't had any problem with #NAT64 in particular--seems to work just as well as any other NAT.

The problem with #DNS64 is that it won't work for IPv4 literals, which bypass DNS completely. And of course you have to use the right DNS servers, which might cause problems with customers that have their own manually set or whatever; hence, my ISP uses #464XLAT instead to simulate a real IPv4 connection.

@tschaefer @noipv6 Now I’m wondering why clatd needs a dedicated IPv6 address. They’re really clear about the requirement, but I’m not finding much information about •why• it’s needed. #IPv6 #464XLAT #clatd

@brouhaha @nygren @paul_ipv6 @iscdotorg
There is at least one technical reason. As long #464xlat is needed you need 2 IP addresses - in case you respect the slaac and DHCPv6 settings - you get only one.
The other arguments(avoid NAT for sharing) may be solved by requesting a prefix.

I don't think that a broken RA/ND behavior in a single case is a good argument for.
My pixels run fine in a IPv6 only WiFi.

So maybe it *is* the #464XLAT thing. If there's two servers, maybe it's connecting with different source addresses (https://www.reddit.com/r/tmobileisp/comments/zlclrf/each_individual_ipv4_connection_sourcing_from/) and getting ignored. Cause #Photon doesn't support #IPv6 😔

So the only solution is to use VPN.

#vrchat #tmobile

>#vrchat keeps "VRChat has stopped responding"-ing
>must be https api (cloudflare) as real-time session (photon) works fine
>dunno whether unity's using #ipv4 or #ipv6
>maybe it has something to do with that funky #464XLAT business
>try ipv6 in hosts file for api.vrchat.cloud
>no change
>try ipv4
>no more problem
>mfw ipv6-based isp has more problems with ipv6 than fake ipv4
:sGrimace: