Windows 11's CLAT functionality is expanded to support non-cellular network interfaces

The expanded support will be tested in the Windows Insider Program first.

Reading time icon 2 min. read


Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more

Windows 11 CLAT

Microsoft announced that it will expand the Compatibility Layer for Address Translation (CLAT) functionality to support non-cellular network interfaces, as part of its goals to improve the IPv6 networks.

CLAT can be used to connect devices to IPv4 networks using IPv6 addresses, and it enables Windows 11 devices to connect to networks that use the IPv6 internet protocol. As the world is moving away from IPv4 networks, CLAT comes in as a liaison to enable such connections.

Microsoft will add support to relevant parts of RFC 7050, RFC 8781, and RFC 8925 standards, as you can see below. It’s worth mentioning that the Redmond-based tech giant will make them available in the Windows Insider Program first.

We are committing to expanding our CLAT support to include non-cellular network interfaces in a future version of Windows 11. This will include discovery using the relevant parts of RFC 7050 (ipv4only.arpa DNS query), RFC 8781 (PREF64 option in RAs), and RFC 8925 (DHCP Option 108) standards. Once we do have functionality available for you to test in Windows Insiders builds, we will let you know.

Microsoft

However, you’ll have to keep in mind that CLAT has some limitations in Windows 11, and it might not automatically work with other network interface types, such as Wi-Fi, for instance. In this case, you might be put in a situation where you’ll have to enable and configure the functionality manually.

To do it, you’ll need to:

  1. Open Windows 11’s Command Prompt as Admin.
  2. Type in the following command: netsh interface ipv6 show prefixpolicies
  3. Look for 464XLAT and enable it.

Windows users are pleased with Microsoft’s decision to expand this functionality’s support, with some of them stating that it will make IPv6-only networks more viable.

While I’ll readily admit to being a critic of Microsoft’s missteps (particularly regarding IPv6 support), that means I also have to acknowledge the wins, too. Thank you for listening to the community on this! This will make IPv6-only networks a lot more viable.

Windows user

More about the topics: Windows 11, Windows Update