Skip to content
AdminKit

464XLAT

What is 464XLAT?

464XLAT, defined in RFC 6877, lets an IPv4-only app keep working on a mobile network that only assigns IPv6 addresses, by combining a device-side translator (CLAT) with a provider-side NAT64 gateway (PLAT). AdminKit's My IP tool shows whether a connection is actually IPv6-only, the condition that makes 464XLAT necessary in the first place.

By AdminKit team, Netbase JSC · Updated

464XLAT, defined in RFC 6877 (tracked on the IETF Datatracker), lets an IPv4-only application keep working on a network that only assigns IPv6 addresses, by combining two translators: a CLAT (customer-side translator) running on the device itself, and a PLAT (provider-side translator) — typically a NAT64 gateway, defined in RFC 6146 — run by the network operator. The CLAT translates an app’s outgoing IPv4 traffic into IPv6 locally, the PLAT translates it back to IPv4 at the network edge to reach the IPv4 internet, and replies retrace the same path in reverse. This solves a gap that NAT64 and DNS64 alone leave open: DNS64 only works when an app does a DNS lookup and gets a synthesized address back, but some apps connect to a hardcoded IPv4 literal address or skip DNS entirely, giving DNS64 no hostname to synthesize an answer for. The CLAT intercepts that traffic before it ever reaches DNS. Apple’s guidance on supporting IPv6-only networks shows the app-side view of the same gap: apps that rely on IPv4-specific APIs or hardcoded IP addresses need changes, while servers on the wider internet stay reachable to IPv6-only devices through DNS64/NAT64. 464XLAT is widely used on mobile networks, as the Asia-Pacific Network Information Centre’s own mobile-operator deployment guidance documents, and has shipped as a built-in CLAT in Android since version 4.3, letting carriers run IPv6-only radio networks while still supporting IPv4-only apps and websites without every app needing its own IPv6 support.

464XLAT is part of AdminKit’s IP & network cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

What problem do the CLAT and PLAT solve together in 464XLAT?

The CLAT, running on the device, translates an app's outgoing IPv4 traffic to IPv6 locally, and the PLAT -- typically a NAT64 gateway run by the network operator -- translates it back to IPv4 at the network edge, so an IPv4-only app keeps working on an IPv6-only network.

Why isn't NAT64 and DNS64 alone enough for every IPv4-only app?

Because DNS64 only synthesizes an IPv6 address when an app actually performs a DNS lookup; an app that connects to a hardcoded IPv4 literal address or skips DNS entirely gets no synthesized address to use, which is the gap the device-side CLAT closes.

Which platform ships a built-in CLAT?

Android has shipped a built-in CLAT since version 4.3, letting mobile carriers run IPv6-only radio networks while still supporting IPv4-only apps and websites.

Does 464XLAT replace NAT64?

No -- 464XLAT is built on top of NAT64 and depends on a PLAT, which is typically a NAT64 gateway; it adds a device-side translator rather than replacing the network-side one.