goetz2d ago

#464XLAT and #NAT64 on #Mikrotik routers.

https://forum.mikrotik.com/t/nat64-and-464xlat-on-ros-how-to/267046

Please have this out of the box available?
@mikrotik@tiktube.com @mikrotik

#IPv6 #IPv6mostly

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
Anderson SilvaJul 11

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
Anderson SilvaJun 28

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

#IPv6 #IPv6Mostly

Beni HB9HNTMar 16
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
Show threadKnut KarevollNov 27, 2024
@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
Show threadMynacolOct 29, 2024
@lattera
Well, the respective network could send a #NAT64 prefix and add DHCP (v4) Option 108 and Android should do #464XLAT and disable native IPv4.
(That requires controlling the network, yes)
Hugo Slabbert ⚠️Oct 18, 2024

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.

#IPv6 #NAT64 #464XLAT

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
Colin Cogle Oct 4, 2024

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

Thomas SchäferSep 10, 2024

ipv4only.arpa 💀 ?

PREF64

https://datatracker.ietf.org/doc/draft-buraglio-deprecate7050/

#clat
#464xlat
#ipv6only

Discouraging use of RFC7050 for Discovery of IPv6 Prefix Used for IPv6 Address Synthesis

RFC7050 describes a method for detecting the presence of DNS64 and for learning the IPv6 prefix used for protocol translation (RFC7915). This methodology depends on the existence of a well-known IPv4-only fully qualified domain name "ipv4only.arpa.". Because newer methods exist that lack the requirement of a higher level protocol, instead using existing operations in the form of native router advertisements, discovery of the IPv6 prefix used for protocol translation using RFC7050 should be discouraged. RFC7050 MAY only be used if other methods (such as RFC8781]) can not be used.

IETF Datatracker
Show threadAdrian OffermanAug 22, 2024

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-networks

Windows 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.

#IPv6

Microsoft extends Windows 11 464XLAT support to include fixed-line networks | Cybersecurity | SIDN

Microsoft has announced plans to extend support for the 464XLAT transition mechanism in Windows 11. At present, Windows 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.

SIDN - The company behind .nl