Mailing List Archive

I've had no luck getting it to work either on an IPv6-only LAN with DNS64 and NAT64.
Ross


Sent from my Samsung device

-------- Original message --------
From: Mikael Abrahamsson <swmike@swm.pp.se>
Date: 27/07/2017 3:50 PM (GMT+00:00)
To: ipv6-ops@lists.cluenet.de
Subject: Win10 update CLAT


Hi,

I did all the updates in Win10 because of the claim that CLAT would be
included in the latest updates. I can't make it work. DNS64+NAT64 works
correctly, but I can't ping IPv4 literals (expected behaviour of a host on
IPv6-only+DNS64+NAT64 without CLAT).

https://blogs.technet.microsoft.com/networking/2017/07/13/core-network-stack-features-in-the-creators-update-for-windows-10/

"Improved 464XLAT support
464XLAT was originally designed for cellular only scenarios since mobile
operators are some of the first ISPs with IPv6 only networks.  However,
some apps are not IP-agnostic and still require IPv4 support.  Since a
major use case for mobile is tethering, 464XLAT should provide IPv4
connectivity to tethered clients as well as to apps running on the mobile
device itself. Creators Update adds support for 464XLAT on desktops and
tablets too. We also enabled support for TCP Large Send Offload (LSO) over
464XLAT improving throughput and reducing CPU usage."

Is there anything specific I need to do to enable this?

--
Mikael Abrahamsson    email: swmike@swm.pp.se

On Thu, 27 Jul 2017, Ross Chandler wrote:

> I've had no luck getting it to work either on an IPv6-only LAN with
> DNS64 and NAT64. Ross

After reading the text again, I speculated that it was Win10 mobile only.
I therefore dug up a win10 mobile phone I have, and updated it, and tried
to connect to NAT64+DNS64 wifi I have. After updating it to 1703 I still
can't see any CLAT being detected in any way (for instance test-ipv6.com).

So the only thing I can think of is that the CLAT is mobile-only on win10
mobile only. So I put in a SIM card in it and tried to create a new APN,
and it indeed does have a new APN type called "IPv4v6XLAT" (in addition to
"IPv4", "IPv6" and "IPv4v6"). Unfortunately my mobile provider is dual
stack and doesn't offer NAT64+DNS64 (at least not on its default APN) so I
can't test it.

So my take on this is that it's a Win10 only feature, and it's mobile
only.

Pity.

--
Mikael Abrahamsson email: swmike@swm.pp.se

> On 27 Jul 2017, at 18:27, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>
> So my take on this is that it's a Win10 only feature, and it's mobile only.
>
> Pity.
>

It should be working on desktops too though because the blurb says “Creators Update adds support for 464XLAT on desktops and tablets too.”

Ross

Am Donnerstag, 27. Juli 2017, 19:36:58 CEST schrieb Ross Chandler:

>
> It should be working on desktops too though because the blurb says “Creators
> Update adds support for 464XLAT on desktops and tablets too.”
>
> Ross

My interpretation of this sentence is the same. So I tried it today afternoon
with IPv6-only WIFI and DNS64/NAT64 - but no success for ping 8.8.8.8.

Regards,
Thomas

> On 28 Jul 2017, at 22:19, Marcus Keane <marcus.keane@microsoft.com> wrote:
>
> This functionality is only enabled when a WWAN interface is installed in the device, and the Mobile Operator has enabled 464xlat on the network. The blog entry is being updated to reflect this. FWIW, I understood the same as you when reading the article.
> Marcus

Thanks for the confirmation. Here’s hoping MS extends this to all interfaces where SLAAC is used and the network signalled DNS server supports DNS64 and a connectivity verification check confirms the NAT64 is working.

Ross