November 22, 2026

Microsoft Expands Windows IPv6 Capabilities with New CLAT Support for Wi-Fi and Ethernet Interfaces

In a significant move for the evolution of enterprise networking, Microsoft has officially introduced IPv6 Windows CLAT support for Wi-Fi and Ethernet interfaces. The development marks a pivotal shift in how the Windows operating system handles the transition from legacy IPv4 protocols to modern IPv6-only environments. To discuss the implications of this update and the technical hurdles overcome during its implementation, Jim Alumbaugh, Technical Program Manager for Windows Networking Protocols at Microsoft, recently joined industry experts Ed, Nick, and Tom on a featured technical broadcast.

The introduction of CLAT (Customer-side Translator) for local area network (LAN) and wireless interfaces represents a major milestone for IT administrators who have long sought to simplify their network architectures. For years, the industry has grappled with the "dual-stack" approach—maintaining both IPv4 and IPv6 concurrently—which, while functional, often doubles the management overhead and security surface area for enterprise environments. The new support in Windows aims to facilitate the transition to "IPv6-mostly" networks, allowing organizations to phase out IPv4 without breaking compatibility for legacy applications.

The Evolution of 464XLAT and Windows Networking

To understand the weight of this announcement, it is essential to look at the mechanics of 464XLAT, the architecture of which CLAT is a primary component. In an IPv6-only or IPv6-mostly network, the infrastructure typically utilizes NAT64 (Network Address Translation 64) and DNS64 to allow IPv6-capable devices to communicate with the IPv4-only internet. However, many legacy applications and services are "IPv4-literal," meaning they hardcode IPv4 addresses or rely on legacy sockets that cannot natively communicate over an IPv6 stack.

CLAT serves as the solution to this "last mile" compatibility problem. It resides on the client device, creating a virtual IPv4 interface that intercepts outgoing IPv4 traffic from legacy applications, translates it into IPv6 packets, and sends them across the IPv6-only network to a provider-side translator (PLAT). While Windows has supported CLAT on cellular (WWAN) interfaces for several years—driven by the rapid adoption of IPv6 by mobile carriers—the extension of this support to Wi-Fi and Ethernet is a direct response to the needs of the modern enterprise campus.

During the discussion, Alumbaugh highlighted that the integration of CLAT into the broader Windows networking stack is not merely a port of existing cellular technology. Bringing this functionality to Wi-Fi and Ethernet required addressing the diverse and often unpredictable nature of corporate and home network environments, where hardware and driver variations are significantly more complex than the controlled environment of cellular modems.

Accelerating the Migration to IPv6-Mostly Networks

The primary driver behind this update is the industry’s push toward RFC 8925, which defines the "IPv6-Only Preferred" option for DHCPv4. This mechanism allows a network to signal to a connecting device that it is capable of operating entirely on IPv6. If the device supports CLAT, it can disable its IPv4 stack for the interface, relying instead on the translation layer for any remaining IPv4 needs.

Alumbaugh explained that this "IPv6-mostly" configuration is the current gold standard for enterprise migration. It provides a safety net: if a device does not support the new protocols, it can still fall back to standard IPv4. However, for modern Windows devices, the enablement of CLAT means that the native IPv4 stack can essentially remain dormant. This reduction in protocol complexity has far-reaching benefits, including improved routing efficiency, a reduction in the exhaustion of private IPv4 address space (RFC 1918), and a more streamlined security posture.