@tschaefer Thats great news.

This would enable to get rid of #DNS64 .

But why should I make a step back. I'm running Windows IPv6-only nowadays. 😎

Don't have any app that requires IPv4 literals.

Choices ... 🤔

IPv6-mostly Networks: Deployment and Operations Considerations

This document discusses a deployment scenario called "an IPv6-mostly network", when IPv6-only and IPv4-enabled endpoints coexist on the same network (network segment, VLAN, SSID etc). The proposed approach enables smooth and incremental transition from dual-stack to IPv6-only network by allowing IPv6-capable devices to remain IPv6-only while the network is seamlessly supplying IPv4 to those that require it.

IETF Datatracker

@MarkTwoFive
If your device can run without IPv4 it will not assign an IPv4 address.
The network provides a NAT64 Gateway to reach the legacy internet

e.g. MacOS, iOS, Android, Dev Version of Linux with NetworkManager.

#464xlat #NAT64 #DNS64

@tschaefer RFC7050 #DNS64 prefix discovery support is not forseen as this will be deprecated in the near future.

Extending the Vector Packet Processing Engine

I've been building core networking components to leverage VPP more fully as a branch router. Here is an overview of that work.

https://enigmatick.social/objects?uuid=b5cfe32e-e1ba-40da-80a1-e6f5bcfb6149

Enigmatick

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

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

#chromeos #dns64 #ipv6mostly

One of the annoyances with #NAT64 is that when some site publishes an #IPv6 AAAA record, but their IPv6 server is down and the IPv4 server is up, there's no "happy eyeballs" fallback to IPv4. Because the AAAA record exists, #DNS64 doesn't provide a mapping to IPv4.

It can be worked around by manually adding an /etc/hosts entry for the broken site.

Today's broken site is www.fsf.org. Hey @fsf - your IPv6 server is refusing connections 😉

@quad9dns Is there a chance to provide a DNS64 resolver service? Currently, the only big ones are Google and Cloudflare. Neither are palatable. #DNS64
Great, the website of the airport of Zürich doesn't work on #ipv6 even though www.flughafen-zuerich.ch resolves to an ipv6 address (via a couple of CNAMEs). That's the worst type of #ipv6 fail, because it also breaks #dns64 and #nat64 on my ipv6 only network.