Mission: Connect to a device on the LAN (Local Area Network)
Scenario: #IPv6mostly network - supported clients get only #IPv6 addresses due to DHCP option 108 -> #464XLAT
Roku app:

Update:
Während ich kurz telefonieren war, hat @jana ein CLAT-Container gebaut, der in meinem v6only Kubernetes tut. https://codeberg.org/itz_jana/tundra-nat64-container

Einziges Problem: Wir haben noch ein hässliches NAT66. #ipv6 #uplink26 #464xlat

Windows CLAT Enters Private Preview: A Milestone for IPv6 Adoption | Microsoft Community Hub

IPv6 Adoption: A Global Shift Since its standardization in the late 1990s, IPv6 has steadily gained traction. The last 15 years, especially since World IPv6...

TECHCOMMUNITY.MICROSOFT.COM

#NetworkManager just got #464XLAT CLAT support merged in.
IMHO this is a major step for #IPv6-only/mostly support on Linux, with NetworkManager likely being the most used network tool on Linux desktops out there.
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2107

Huge thanks to @mary who started the implementation and bgalvani who brought it over the finish line, and of course everyone else who contributed to it someway.

Add support for CLAT using a BPF program (!2107) · Merge requests · NetworkManager / NetworkManager · GitLab

Summary Implements a CLAT (part of a larger 464XLAT ipv6 transition mechanism) in NetworkManager

GitLab

#NetworkManager will now include #CLAT capabilities: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2107 is now merged, functionality will be available on a future release.

Thanks to everyone involved 🙂

#IPv6 #464XLAT #IPv6mostly #Linux

Add support for CLAT using a BPF program (!2107) · Merge requests · NetworkManager / NetworkManager · GitLab

Summary Implements a CLAT (part of a larger 464XLAT ipv6 transition mechanism) in NetworkManager

GitLab
NAT64 and 464XLAT on ROS how-to

Here is a working NAT64 solution for homelab folks wanting to experiment with IPv6-only, or their provider only offers IPv6 with IPv4 over CG-NAT. Full 464XLAT operation is achieved when the client devices include a CLAT, such as Apple devices. This solution does require the ISP provide an IPv4 address, so it won’t work if the provider is IPv6-only and doesn’t provide NAT64 in their network, Ive read that some do. My network is a fairly typical dual-stack setup where my ISP offers CG-NATed IPv4...

MikroTik community forum

Does anyone know how to run an #IPv6 #464XLAT #CLAT client inside a #Proxmox LXC container? clatd ( https://github.com/toreanderson/clatd ) doesn't work because tayga is unable to create a tun interface inside the LXC and I have some software to run that, you guessed it, is still stuck on the obsolete protocol + I don't want to create a full VM just for it.

- cc @apalrd

GitHub - toreanderson/clatd: A 464XLAT CLAT implementation for Linux

A 464XLAT CLAT implementation for Linux. Contribute to toreanderson/clatd development by creating an account on GitHub.

GitHub

WAIT A MINUTE: #Steam working with #464XLAT in #Linux ??? Am I delusional??? 🤯

#IPv6 #IPv6Mostly

Finally I convinced my Linux laptop to adhere the DHCPv4 Option 108 and use #clat to connect to IPv4 addresses - I'm not even sure whether I have any applications that insist on using IPv4... #ipv6 #464xlat
@Tubsta Anyone who want to try #IPv6only can just disable IPv4 with any ISP that provides native IPv6. So there is no appetite for such an ISP. It is more the ISPs that reject dual stack and switch to #464xlat and #IPv6mostly