Manuel AltherrApr 7
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
Show threaddrkApr 5
#trythisathome but also #ymmv. my config is perhaps not the most exotic, but does use the sfp-wan interface, contains a jool-based #ipv6mostly setup (thank you @Oskar456), wireguard, of course #unbound (+adblock) , chrony, and some other stuff.
Show threadThomas SchäferApr 4

@kasperd

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

#ipv6mostly #ipv6only #ipv6 #clat #windowspreview

Thomas SchäferApr 3

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.

#windows11 #clat #ipv6 #ipv6mostly #ipv6only

Thomas SchäferApr 3

https://packetpushers.net/podcasts/ipv6-buzz/ipb197-slaac-and-the-end-of-dhcp/

#podcast #ipv6 #ipv6mostly

IPB197: SLAAC and the End of DHCP? | Packet Pushers

Today our hosts discuss the essential role of Stateless Address Autoconfiguration (SLAAC) in successfully deploying an IPv6 mostly network. SLAAC is required to assign unique IPv6 address to the Customer-side Translator (CLAT) which allows devices to operate on IPv6. However, enterprise operators might prefer using DHCPv6 for network tracking and accountability, trapping them in complex dual-stack environments.

Show threadgoetzMar 29

@harald @chrysn
They only miss a CLAT, and need a DNS64 server.

#chromeos #dns64 #ipv6mostly

Anderson SilvaMar 21
Mission: Connect to a device on the LAN (Local Area Network)
Scenario: #IPv6mostly network - supported clients get only #IPv6 addresses due to DHCP option 108 -> #464XLAT
Roku app:
Show threadThomas SchäferMar 14

@debian

still without the recent version of tayga

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107302

#ipv6only #nat64 #tayga #debian #ipv6 #ipv6mostly

#1107302 - New upstream fork - Debian Bug report logs

Show threadgoetzMar 6
@nSonic kannst Du genaueres sagen? Welche Dienste? Nutze #Azure / MS in einem #IPv6mostly setup und sehe keine Probs.
#Android hat IPv6only addressing.
Show threadgoetzMar 3

@tschaefer
The best statement of every Jen presentation:
"You are not operating IPv6 until you turn IPv4 off"

#IPv6mostly #IPv6only #IPv6 #enterprise