One of the annoyances with #NAT64 is that when some site publishes an #IPv6 AAAA record, but their IPv6 server is down and the IPv4 server is up, there's no "happy eyeballs" fallback to IPv4. Because the AAAA record exists, #DNS64 doesn't provide a mapping to IPv4.

It can be worked around by manually adding an /etc/hosts entry for the broken site.

Today's broken site is www.fsf.org. Hey @fsf - your IPv6 server is refusing connections 😉

One of the annoyances with #NAT64 is that when some site publishes an #IPv6 AAAA record, but their IPv6 server is down and the IPv4 server is up, there's no "happy eyeballs" fallback to IPv4. Because the AAAA record exists, #DNS64 doesn't provide a mapping to IPv4.

It can be worked around by manually adding an /etc/hosts entry for the broken site.

Today's broken site is www.fsf.org. Hey @fsf - your IPv6 server is refusing connections 😉

And yes, using NAT64 technically goes against the spirit of No-NAT November, but the alternative would be to stop myself from using half of the internet for 30 days without learning anything other than which websites and services break without IPv4, which gets boring very quickly.

Either way, the next thing I want to look at is PREF64, as well as building a CLAT on operating systems that don't natively support them, in case they run software relying on hard-coded IPv4 addresses. 😎

#IPv6 #NAT64

Edit

The following blog post was very inspiring for me, thanks @alexhaydock for sharing this. :)

https://blog.infected.systems/posts/2024-12-01-no-nat-november/

And yes, using NAT64 technically goes against the spirit of No-NAT November, but the alternative would be to stop myself from using half of the internet for 30 days without learning anything other than which websites and services break without IPv4, which gets boring very quickly.

Either way, the next thing I want to look at is PREF64, as well as building a CLAT on operating systems that don't natively support them, in case they run software relying on hard-coded IPv4 addresses. 😎

#IPv6 #NAT64

Edit

The following blog post was very inspiring for me, thanks @alexhaydock for sharing this. :)

https://blog.infected.systems/posts/2024-12-01-no-nat-november/

Huh ... just enabled DNS64 and DHCP option 108 on my OPNsense to see if my phones would enable their CLAT, guessing that I would need to do more work, but it just works™️.

The iPhone reports 192.0.0.3 as it's IPv4 and 192.0.0.1 as gateway, and the Android doesn't show any IPv4 (but 255.0.0.0 as next hop in traceroute?).

Either way, that's another two IPv6-only devices, I'm actually making progress. 😁

#IPv6 #NAT64

Installed our new router box yesterday and switched our LAN from dual-stack to #IPv6 only with #DNS64 + #NAT64

Did quite a lot of this one-handed, as Alonso fell asleep on my arm. 🐶💤

Oh cool. We just tested and #WebRTC with #Jitsi works over #NAT64

I'd heard WebRTC can be problematic with #NAT64, and the fact that Jitsi has dropped the IPv6 AAAA records for meet.jit.si and closed some recent IPv6 bug reports as WONTFIX didn't give me a lot of confidence. 😟

However, jitsi worked fine just now with one user on mobile (IPv4-only) and another on NAT64.

😀

Oh cool. We just tested and #WebRTC with #Jitsi works over #NAT64

I'd heard WebRTC can be problematic with #NAT64, and the fact that Jitsi has dropped the IPv6 AAAA records for meet.jit.si and closed some recent IPv6 bug reports as WONTFIX didn't give me a lot of confidence. 😟

However, jitsi worked fine just now with one user on mobile (IPv4-only) and another on NAT64.

😀

Installed our new router box yesterday and switched our LAN from dual-stack to #IPv6 only with #DNS64 + #NAT64

Did quite a lot of this one-handed, as Alonso fell asleep on my arm. 🐶💤

"oh, we could have simply used #NAT64".

Don't take it too serious.. =)

@arch