#ipv6mostly — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #ipv6mostly, aggregated by home.social.
-
An diesem langen Wochenende habe ich mal wieder mir Zeit genommen, um etwas an meinem Heimnetz herumzuspielen und den #RaspberryPi mal wieder anzuwerfen. #IPv6mostly war diesmal mein Testgebiet. Mit CoreDNS, Tayga und KEA DHCP-Server hat das ganze dann irgendwann doch recht gut funktioniert. Ich war überrascht wie stark an einem die KI (hier Gemini) weiterhelfen und ein Tutorial für ein doch spezielles Thema erstellen konnte. Nach etwas gebastel hat es dann doch funktioniert. #DNS64 #NAT64
-
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. -
still without the recent version of tayga
-
It seems to me, they need more testers.
-
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
-
After explaining the current state of affairs with #IPv6 transition mechanisms, I published a tutorial on how to apply all of that in a real network with @news (#VyOS):
https://blog.daknob.net/ipv6-first-with-vyos/
#IPv6First #IPv6Mostly #PPPoE #DHCPv6PD
https://mastodon.social/@antonis/112246775124361251 -
@nuintari My (admittedly cursory) understanding is that it's a transition aid, to smooth the path from #dualstack to #ipv6mostly. ̶A̶n̶ ̶O̶S̶ ̶n̶e̶t̶w̶o̶r̶k̶ ̶s̶t̶a̶c̶k̶ ̶m̶i̶g̶h̶t̶ ̶b̶e̶ ̶r̶e̶l̶u̶c̶t̶a̶n̶t̶ ̶t̶o̶ ̶t̶a̶k̶e̶ ̶t̶h̶e̶ ̶f̶i̶r̶s̶t̶ ̶l̶e̶a̶p̶-̶o̶f̶-̶f̶a̶i̶t̶h̶ ̶t̶o̶ ̶I̶P̶v̶6̶-̶m̶o̶s̶t̶l̶y̶,̶ ̶s̶o̶ ̶t̶h̶e̶ ̶R̶F̶C̶ ̶l̶e̶t̶s̶ ̶t̶h̶e̶ ̶n̶e̶t̶w̶o̶r̶k̶ ̶m̶a̶k̶e̶ ̶t̶h̶e̶ ̶f̶i̶r̶s̶t̶ ̶m̶o̶v̶e̶,̶ ̶p̶o̶s̶i̶t̶i̶v̶e̶l̶y̶ ̶d̶e̶c̶l̶a̶r̶i̶n̶g̶ ̶t̶h̶a̶t̶ ̶I̶P̶v̶6̶ ̶s̶i̶n̶g̶l̶e̶ ̶s̶t̶a̶c̶k̶ ̶s̶h̶o̶u̶l̶d̶ ̶w̶o̶r̶k̶ ̶f̶i̶n̶e̶.̶ ̶A̶ ̶d̶u̶a̶l̶ ̶s̶t̶a̶c̶k̶ ̶n̶e̶t̶w̶o̶r̶k̶ ̶w̶o̶u̶l̶d̶ ̶l̶a̶c̶k̶ ̶t̶h̶a̶t̶ ̶s̶i̶g̶n̶a̶l̶,̶ ̶a̶n̶d̶ ̶t̶h̶e̶ ̶O̶S̶ ̶w̶o̶u̶l̶d̶ ̶b̶e̶h̶a̶v̶e̶ ̶a̶c̶c̶o̶r̶d̶i̶n̶g̶l̶y̶
Essentially, it's like "positive affirmations", but for the next phase of IPv6 transition
-
Rejoice, network operators. Windows 11 will be joining the rest of the world soon in supporting CLAT, #NAT64, and #DNS64 natively. (Currently, CLAT only works on cellular connections.)
Supporting two IP versions has been a pain we’ve had to live with for over a decade, but this will allow network operators to forcibly disable clients’ IPv4 stacks via DHCP/RA, finish #IPv6 switchovers, and run true #IPv6mostly or #IPv6only networks.
We’re one big step closer to killing “legacy IP” for good. :ipv6:
