#464xlat — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #464xlat, aggregated by home.social.
-
@MarkTwoFive
If your device can run without IPv4 it will not assign an IPv4 address.
The network provides a NAT64 Gateway to reach the legacy internete.g. MacOS, iOS, Android, Dev Version of Linux with NetworkManager.
-
#ipv6 #ipv4rip #ipv4 #clat #windows #464xlat #ipv6mostly #ipv6only #ripe92
slide 13/14/15 by Wilhelm Boeddinghaus
https://pretalx.ripe.net/media/ripe-92/submissions/XJWGCT/resources/RIPE92-May-2026-IPv6_MmzPXy4.pdfnow corrected by Microsoft as promised two weeks ago
It is still a experimental version, not released yet. (Build 29599.1000 )
(now you can use several windows hosts in one network segment with clat)
-
Want to help testing #CLAT on Linux and run #networkmanager?
Please tryout:
https://ipv6-pod.info/2026-02/network-manager-clat.html -
Extending the Vector Packet Processing Engine
I've been building core networking components to leverage VPP more fully as a branch router. Here is an overview of that work.https://enigmatick.social/objects?uuid=b5cfe32e-e1ba-40da-80a1-e6f5bcfb6149
-
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-containerEinziges Problem: Wir haben noch ein hässliches NAT66. #ipv6 #uplink26 #464xlat
-
It seems to me, they need more testers.
-
#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/2107Huge 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.
-
@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
-
Kinda fun poking around with some nat64 things while prepping a small internal IPv6-related presentation. I'd been using the automatic CLAT that macOS just runs in the background, but it was a nice surprise to install clatd for a demo on an Ubuntu VM and have it Just Work.
-
I opted to test Windows 11 24H2 for my company. Good news, Wi-Fi 7 works great. I’m connected to my U7-Pro at 5.8 Gbps — not that that will get me too far with the AP connected with 2.5GBaseT and 1 Gbps Internet (download, a pathetic 0.035 Gbps upload over DOCSIS). But hey, it looks nice.
Bad news, @jima and @paulos: the promised “future version of Windows 11” with CLAT support isn’t this one. Windows 11 still insists on using legacy IP despite me shoving DHCPv4 option 108 down its throat.
#Windows #Win11 #Windows11 #24H2 #IPv6 #LegacyIP #IPv6mostly #IPv6only #464XLAT #CLAT #UniFi #WiFi7 #sysadmin #EarlyAdopter
-
also available in English:
Microsoft extends Windows 11 464XLAT support to include fixed-line networks -- New phase in changeover from IPv4 to IPv6 requires appropriate transition mechanisms
https://www.sidn.nl/en/news-and-blogs/microsoft-extends-windows-11-464xlat-support-to-include-fixed-line-networksWindows 11 supports only CLAT for mobile networks, but a future version will also provide support for other network interfaces. It will then be possible to enable #464XLAT on fixed-line networks as well.
-
op SIDN.nl:
Microsoft breidt 464XLAT-ondersteuning in Windows 11 uit naar vaste netwerken -- Nieuwe fase in overgang van IPv4 naar IPv6 vraagt om specifieke transitiemechanismen
https://www.sidn.nl/nieuws-en-blogs/microsoft-breidt-464xlat-ondersteuning-in-windows-11-uit-naar-vaste-netwerkenWaar Windows 11 nu alleen CLAT ondersteunt voor mobiele netwerken, komt deze mogelijkheid in een toekomstige versie ook voor andere netwerkinterfaces beschikbaar. Dat maakt het straks mogelijk om #464XLAT ook op vaste netwerken in te schakelen.
-
@thatnateguy Is the question about carrier-grade NAT66 or carrier-grade NAT44? Or even #464XLAT ?
-
I've tried to summarize the current state of the art for IPv6-First and IPv6-Only Access Networks in my blog post here: https://blog.daknob.net/do-you-really-need-ipv4-anymore/
Let me know how it went for you, what problems you may have ran into, and whether something is missing! I'm also happy to answer questions or help with ideas.
-
@ktims at the very least I would suspect this is going to start adding customer pressure for AWS to actually provide #IPv6 support to their services that are still IPv4-only, or are missing v4/v6 parity. Don't get me wrong: I'm here for the move and you just need to make the call at some point, but that doesn't mean it's not still a bit rude to present your customer with a lower and higher priced choice on the surface, but then simply remove the lower cost choice for a non-trivial subset of your products 😝
But, the market is definitely starting to normalize (source Hilco for this screenshot). It's definitely interesting to see how different forces and stakeholders are starting to interact.
I mean, we had the big content shops like Google, FB, Netflix etc. providing v6 at their edges for a good while, with mobile picking up a good amount on the client side. The CDNs are also in there with generally making it fairly easy to turn up dual stack on their edges.
Residential seems to be trucking along and gaining better adoption, where chunks of newer RGs and such seem to actually be getting to Just Works territory and residential users who don't and shouldn't have to care are getting v6 connectivity as well.Then you have your government forces like DoD and other US fed memos and mandates, and the recently-announced Czech timeline, with e.g. the US reqs starting to push some SaaS and enterprise app providers to get their house in order.
The laggards, imho, have been the large public cloud providers, the developer space in general, and enterprise. With AWS pushing v4 pricing, we now have a more concrete business driver, imho, that will start to push developers as well as infrastructure & platform types to get IPv6 familiarity, with a possible second order of creating more IPv6 demand in the enterprise space for those devs to be able to access as well as test against their now v6-enabled service edges.
It's definitely an interesting time.
Anecdotally I'm seeing the leading edge of the conversation shift away from the earlier v6 tunnels & experimentation, and even from just dual stack, to folks poking at #IPv6-only or #IPv6-mostly, with way more conversations around #NAT64, #DNS64, and #464XLAT popping up in enthusiast spaces.
-
After toiling for a few hours, I've managed to achieve a working #Palworld server on my #IPv6only #k8s cluster. The server is responsive on both modern and legacy IP, which I think might be fairly unique, since the game server doesn't listen on #IPv6 and I suspect the game client doesn't connect on IPv6 either.
This works using a Tundra-NAT64 CLAT sidecar, doing #464XLAT, with internal #NAT66 DNAT and SNAT in an unwholesome combo.
Occasionally, it pays to have a strong networking background.
-
Safari on iOS 16.6 is still not capable of using the CLAT portion the OS sets up in a 464XLAT compatible network.
The caveats mentioned in https://labs.ripe.net/author/ondrej_caletka_1/deploying-ipv6-mostly-access-networks/ still apply. Configuring DNS64 is still a no-no for various reasons.