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
@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 ... 🤔

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.
@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.
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
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 😉