As always, things didn't go as smoothly as I had hoped.
2 additional discoveries:
1. The #macOS and #iOS #CLAT engine seems to randomly stop working after some time? The interface still exists, but I can't reach IPv4 addresses anymore. #NAT64 is still available and working though. Haven't yet seen the issue on #Android.
2. Apple Homepods also have CLAT! They just decided to go IPv6-only, which I only noticed because #Homeassistant couldn't connect to them anymore.
#macos #ios #clat #nat64 #android #homeassistant
I've successfully installed a #NAT64 server and a #DNS64 Bind9 server in my homelab.
I set the DHCP Option 108 and observed my #iOS and #Android devices immediatly going #IPv6-only and enabling its #CLAT engine.
The most surprising part though was that #macOS did the same.
I've read online multiple times, that it also requires an option in the Router Advertisement, which I currently can't set. But no, it didn't need it and also started CLAT.
Now if only #Windows would do the same...
#nat64 #dns64 #ios #android #ipv6 #clat #macos #windows
#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
#ripe86 #ipv6 #tutorial #ipv6basics #ipv6only #ipv6transition #dualstack #uptodate #nat64 #464xlat #dslite #video #pdf
The #NAT64 support that has been contributed to the Unbound project has now been merged into the main branch. #DNS #OpenSource https://github.com/NLnetLabs/unbound/pull/722
Having a VPN with #NAT64 and #DNS64 is a great way to see what software is still broken in 2023. Ridiculous.
Hey, popular game store! It's 2023! Migrating from gethostbyname to getaddrinfo really isn't that hard. Do you need to hire me so that I can do those 10 minutes of trivial work for you, since apparently you have been unable to since 2014(!!!) when people reported it.
Using an #ipv6 only mobile #iot network and want to connect to #azure #iothub? Not a problem if you have a carrier like #telstra (Australia) that supports #nat64, as in my recent blog article using the #nordic #thingy91 https://purple.telstra.com/blog/device-authentication-with-nordic-thingy-91-and-azure-iot-hub
#ipv6 #iot #nordic #azure #IoTHub #telstra #nat64 #Thingy91
Yes, one more!
#nat64
https://nitter.net/Emirage6/status/1638983244778536960
#nat64 #ipv6memes #ipv6only #ipv6
@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.
Curious what's coming up in the next release of your favourite #DNS resolver? #Unbound #EDE #SVCB #NAT64 #OpenSource https://github.com/NLnetLabs/unbound/milestone/2
#dns #unbound #ede #SVCB #nat64 #opensource
@hagedose68 There are other #NAT64 options, such as running Jool on a server. That's what we are doing for a smallish network as a first step.
So far we have only deployed #IPv6 in dual-stack mode. I really want to push for IPv6-only now, but I'm not sure if we have all the necessary pieces in place. We can set up #DNS64 on our #Infoblox cluster, but I'm not sure if any of our Cisco routers are actually capable of doing #NAT64.
#CiscoLiveEMEA
#ipv6 #dns64 #infoblox #nat64 #ciscoliveemea