464XLAT and Cellular IPv4 Connectivity
Overview
This document explains 464XLAT support on Meraki gateways running MG26.2.2 or later. It covers when 464XLAT is used to provide IPv4 connectivity over a cellular provider’s IPv6 network and how to check its status in Dashboard.
Some cellular service providers use IPv6 networks while continuing to offer access to IPv4 services. One way they do this is through 464XLAT. Supported MGs can use 464XLAT as part of their cellular IPv4-as-a-Service capability.
For most users, the important result is IPv4 connectivity—not which method the provider uses to deliver it. The MG may receive native IPv4 from the provider, or it may use 464XLAT when native IPv4 is unavailable.
Requirements
Supported Models
-
MG52, MG52E, MG51, MG51E, MG41 and MG41E
Firmware Version
-
MG 26.2.1 and later
Configuration
No separate 464XLAT setting is required. The MG automatically enables the capability when it’s powered on, and no APN is applied on dashboard/LSP or an APN configured with the IPv4v6 IP type.
If you already use one of these configurations, you do not need to change your APN settings to use this feature.
How the MG provides IPv4 connectivity
With an IPv4v6 APN, the MG requests both IPv4 and IPv6 service when it establishes a cellular data session.
-
If the provider supplies native IPv4, the MG uses it.
-
If the provider supplies IPv6 but supports 464XLAT instead of native IPv4, the MG can use 464XLAT to reach IPv4 services.
A provider may supply native IPv4 in one data session and require 464XLAT in another. This change does not, by itself, indicate a problem with the connection.
Check whether 464XLAT is in use
In Dashboard, open the cellular data session on the Uplinks tab. The 464XLAT Active status appears when the MG is currently using 464XLAT.
If 464XLAT Active is not shown, the MG may be using native IPv4. Check the connection’s IPv4 status before treating the absence of the 464XLAT indicator as a fault.