#clat — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #clat, aggregated by home.social.
-
Some statements won't be true anymore within the next three weeks. 🤗
https://pretalx.ripe.net/media/ripe-92/submissions/XJWGCT/resources/RIPE92-May-2026-IPv6_KbCCKtH.pdf
Microsoft announced fixes for their #clat implementation 👍
"We should have a build available to test within 2-3 weeks".
-
Some statements won't be true anymore within the next three weeks. 🤗
https://pretalx.ripe.net/media/ripe-92/submissions/XJWGCT/resources/RIPE92-May-2026-IPv6_KbCCKtH.pdf
Microsoft announced fixes for their #clat implementation 👍
"We should have a build available to test within 2-3 weeks".
-
Some statements won't be true anymore within the next three weeks. 🤗
https://pretalx.ripe.net/media/ripe-92/submissions/XJWGCT/resources/RIPE92-May-2026-IPv6_KbCCKtH.pdf
Microsoft announced fixes for their #clat implementation 👍
"We should have a build available to test within 2-3 weeks".
-
Some statements won't be true anymore within the next three weeks. 🤗
https://pretalx.ripe.net/media/ripe-92/submissions/XJWGCT/resources/RIPE92-May-2026-IPv6_KbCCKtH.pdf
Microsoft announced fixes for their #clat implementation 👍
"We should have a build available to test within 2-3 weeks".
-
Some statements won't be true anymore within the next three weeks. 🤗
https://pretalx.ripe.net/media/ripe-92/submissions/XJWGCT/resources/RIPE92-May-2026-IPv6_KbCCKtH.pdf
Microsoft announced fixes for their #clat implementation 👍
"We should have a build available to test within 2-3 weeks".
-
I occupied *the* windows #CLAT address.
-
DAD works, but nothing more.
Or in other words: At the moment it is not possible to use more than one Windows-PC with IPv6-mostly-support (Preview only ) in a IPv6-mostly or IPv6-only Network.
By accident a host may use one of the other mapped IPv4 addresses (out of 192.0.0.0/29) . But in general it takes the first one anywhere.
and W.B. is right: MS has to fix that problem before it gets released for the masses
-
Falls jemand in München und Umgebung (habe d-ticket) einen Rechner mit dem Betakanal des Windows-Insider-Programm am Laufen hat, ich wäre über einen CLAT Test (via WLAN) mit zwei Rechnern sehr erfreut. Ein mobiler IPv6-mostly Hotspot und mein Rechner stehen zur Verfügung.
Bitte privat antworten. -
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?
-
It seems to me, they need more testers.
-
It seems to me, they need more testers.
-
It seems to me, they need more testers.
-
It seems to me, they need more testers.
-
It seems to me, they need more testers.
-
Tested the #clat implementation of NetworkManager, there seems to be a issue when multiple interfaces are up and connected, but otherwise it's working quite well:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2107 -
CLAT 2026 results declared; candidates can access scorecards and submit grievances via committee portal https://english.mathrubhumi.com/education/news/clat-2026-results-declared-grievance-redressal-committee-formed-koz17cem?utm_source=dlvr.it&utm_medium=mastodon #CLAT2026 #CLAT #ExamResults #Scorecards
-
CLAT 2026 results declared; candidates can access scorecards and submit grievances via committee portal https://english.mathrubhumi.com/education/news/clat-2026-results-declared-grievance-redressal-committee-formed-koz17cem?utm_source=dlvr.it&utm_medium=mastodon #CLAT2026 #CLAT #ExamResults #Scorecards
-
CLAT 2026 results declared; candidates can access scorecards and submit grievances via committee portal https://english.mathrubhumi.com/education/news/clat-2026-results-declared-grievance-redressal-committee-formed-koz17cem?utm_source=dlvr.it&utm_medium=mastodon #CLAT2026 #CLAT #ExamResults #Scorecards
-
Looks like Microsoft is making a little more progress on a CLAT for windows.
-
Windows #CLAT Enters Private Preview: A Milestone for #IPv6 Adoption
https://techcommunity.microsoft.com/blog/networkingblog/windows-clat-enters-private-preview-a-milestone-for-ipv6-adoption/4459534 -
Windows CLAT Enters Private Preview: A Milestone for IPv6 Adoption
-
This draft has now been officially adopted by the v6ops IETF working group and renamed to:
draft-ietf-v6ops-6mopshttps://datatracker.ietf.org/doc/draft-ietf-v6ops-6mops/
Also, a related 464XLAT / CLAT draft to keep an eye on:
https://datatracker.ietf.org/doc/draft-ietf-v6ops-claton/ -
I opted to test Windows 11 24H2 for my company. Good news, Wi-Fi 7 works great. I’m connected to my U7-Pro at 5.8 Gbps — not that that will get me too far with the AP connected with 2.5GBaseT and 1 Gbps Internet (download, a pathetic 0.035 Gbps upload over DOCSIS). But hey, it looks nice.
Bad news, @jima and @paulos: the promised “future version of Windows 11” with CLAT support isn’t this one. Windows 11 still insists on using legacy IP despite me shoving DHCPv4 option 108 down its throat.
#Windows #Win11 #Windows11 #24H2 #IPv6 #LegacyIP #IPv6mostly #IPv6only #464XLAT #CLAT #UniFi #WiFi7 #sysadmin #EarlyAdopter
-
I opted to test Windows 11 24H2 for my company. Good news, Wi-Fi 7 works great. I’m connected to my U7-Pro at 5.8 Gbps — not that that will get me too far with the AP connected with 2.5GBaseT and 1 Gbps Internet (download, a pathetic 0.035 Gbps upload over DOCSIS). But hey, it looks nice.
Bad news, @jima and @paulos: the promised “future version of Windows 11” with CLAT support isn’t this one. Windows 11 still insists on using legacy IP despite me shoving DHCPv4 option 108 down its throat.
#Windows #Win11 #Windows11 #24H2 #IPv6 #LegacyIP #IPv6mostly #IPv6only #464XLAT #CLAT #UniFi #WiFi7 #sysadmin #EarlyAdopter
-
I opted to test Windows 11 24H2 for my company. Good news, Wi-Fi 7 works great. I’m connected to my U7-Pro at 5.8 Gbps — not that that will get me too far with the AP connected with 2.5GBaseT and 1 Gbps Internet (download, a pathetic 0.035 Gbps upload over DOCSIS). But hey, it looks nice.
Bad news, @jima and @paulos: the promised “future version of Windows 11” with CLAT support isn’t this one. Windows 11 still insists on using legacy IP despite me shoving DHCPv4 option 108 down its throat.
#Windows #Win11 #Windows11 #24H2 #IPv6 #LegacyIP #IPv6mostly #IPv6only #464XLAT #CLAT #UniFi #WiFi7 #sysadmin #EarlyAdopter
-
I opted to test Windows 11 24H2 for my company. Good news, Wi-Fi 7 works great. I’m connected to my U7-Pro at 5.8 Gbps — not that that will get me too far with the AP connected with 2.5GBaseT and 1 Gbps Internet (download, a pathetic 0.035 Gbps upload over DOCSIS). But hey, it looks nice.
Bad news, @jima and @paulos: the promised “future version of Windows 11” with CLAT support isn’t this one. Windows 11 still insists on using legacy IP despite me shoving DHCPv4 option 108 down its throat.
#Windows #Win11 #Windows11 #24H2 #IPv6 #LegacyIP #IPv6mostly #IPv6only #464XLAT #CLAT #UniFi #WiFi7 #sysadmin #EarlyAdopter
-
I opted to test Windows 11 24H2 for my company. Good news, Wi-Fi 7 works great. I’m connected to my U7-Pro at 5.8 Gbps — not that that will get me too far with the AP connected with 2.5GBaseT and 1 Gbps Internet (download, a pathetic 0.035 Gbps upload over DOCSIS). But hey, it looks nice.
Bad news, @jima and @paulos: the promised “future version of Windows 11” with CLAT support isn’t this one. Windows 11 still insists on using legacy IP despite me shoving DHCPv4 option 108 down its throat.
#Windows #Win11 #Windows11 #24H2 #IPv6 #LegacyIP #IPv6mostly #IPv6only #464XLAT #CLAT #UniFi #WiFi7 #sysadmin #EarlyAdopter
-
Anyone have any ideas for squeezing a #CLAT into a container? My #homelab #k8s cluster is IPv6-only, and I've discovered this evening that steamcmd is not even asking for AAAA records, meaning my #NAT64 and #DNS64 setup is not effective here. I am not going to dual-stack the whole cluster network just to host one game server, so I'm looking for container-ed options.
IIRC, a requirement for CLAT is being able to carve out a /96 for translation, but k8s assigns a single #IPv6 per pod...
-
@jima @nuintari @godzero I assume we're talking about T-Mobile USA. On one hand, I'm really glad they pushed for an #ipv6only network on their air interface, but you're right it's really annoying that they lock down their modems with no L2 pass through mode. Although I can sort of understand, since it would mean customers would have to run their own #CLAT for legacy IP. But still, the option would be much appreciated; maybe T-Mobile will one day allow for open hardware on home 5G.
-
Introductory post: this is my public sub-account for #IPv6 content; my main account is linked in my profile.
I support the complete roll-out of IPv6, including intermediate efforts like dual-stack support and #NAT64 #DNS64 #CLAT, with the ultimate goal of native IPv6 support in all-new deployments, using RFC standards and best practices.
I support subnets no smaller than /64 (#SLAAC), ISPs should delegate prefixes of at least /56 or /48, and #ICMPv6 should be rate-limited, never blocked.
-
Introductory post: this is my public sub-account for #IPv6 content; my main account is linked in my profile.
I support the complete roll-out of IPv6, including intermediate efforts like dual-stack support and #NAT64 #DNS64 #CLAT, with the ultimate goal of native IPv6 support in all-new deployments, using RFC standards and best practices.
I support subnets no smaller than /64 (#SLAAC), ISPs should delegate prefixes of at least /56 or /48, and #ICMPv6 should be rate-limited, never blocked.
-
Introductory post: this is my public sub-account for #IPv6 content; my main account is linked in my profile.
I support the complete roll-out of IPv6, including intermediate efforts like dual-stack support and #NAT64 #DNS64 #CLAT, with the ultimate goal of native IPv6 support in all-new deployments, using RFC standards and best practices.
I support subnets no smaller than /64 (#SLAAC), ISPs should delegate prefixes of at least /56 or /48, and #ICMPv6 should be rate-limited, never blocked.
-
Introductory post: this is my public sub-account for #IPv6 content; my main account is linked in my profile.
I support the complete roll-out of IPv6, including intermediate efforts like dual-stack support and #NAT64 #DNS64 #CLAT, with the ultimate goal of native IPv6 support in all-new deployments, using RFC standards and best practices.
I support subnets no smaller than /64 (#SLAAC), ISPs should delegate prefixes of at least /56 or /48, and #ICMPv6 should be rate-limited, never blocked.
-
Introductory post: this is my public sub-account for #IPv6 content; my main account is linked in my profile.
I support the complete roll-out of IPv6, including intermediate efforts like dual-stack support and #NAT64 #DNS64 #CLAT, with the ultimate goal of native IPv6 support in all-new deployments, using RFC standards and best practices.
I support subnets no smaller than /64 (#SLAAC), ISPs should delegate prefixes of at least /56 or /48, and #ICMPv6 should be rate-limited, never blocked.
-
CLAT 2020 Is On May 10, Read The Changes In Pattern
Read more: https://bit.ly/2XA3LQ5
#CLAT
