Nach dem Vortrag von Wilhelm Boeddinghaus zu CLAT für Windows auf dem Berliner Adminstammtisch stellt sich mir jetzt die Frage, wo nehme ich 9 Windows11-Kisten mit aktivierten Beta-Insider-Preview her?

#ipv6only #ipv6 #clat #windows11

After the talk by Wilhelm Boeddinghaus about CLAT for Windows at the Berliner Admin Stammtisch I am wondering how to get 9 windows 11 boxes with beta-insider-preview?

Since Microsoft is mapping the 192.0.0.2/29 in to the additional IPv6 address, they only would be able to auto assign 8 of them.
What happens in case of nine Windows boxes in /64 IPv6-mostly network?
Why would the scope of 192.0.0.2/29 expand beyond the individual host?

@kasperd

That's the question.

W.B. was opening my eyes.

I have seen the
::c0:0:100:0
::c0:0:200:0
but I thought it is a kind of leet speak for clat, but it is 192.0.0.1 192.0.0.2 and so on.

So I don't know what happens with 8 or 9 devices, since 192.0.0.0 is already the virtual default gw.

I see. Those are following the /64 mappings in RFC 6052. This is not exactly the purpose that RFC 6052 is intended for. And you already identified the scalability challenges of that approach.

I am guessing they use duplicate-address-detection to ensure two machines don’t pick the same address. if that guess is correct you can easily verify what happens. Just make have a machine use all of the addresses ending in c0:0:0:0 ti c0:0:700:0 before the test machine connects to the network.

If the implementation is even just a little bit sensible it will see that its preferred IPv6 addresses are already in use and pick a random IPv6 address instead. It can still use any address in the 192.0.0.0/29 range locally.

@kasperd

DAD is a must. But probably W.B. nor I had at least two machines in a network. Maybe they count up in the end of the host part.