#dns64 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #dns64, aggregated by home.social.
-
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
-
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
-
A good #dualstack network should still run #dns64 and #nat64, so that it can fully support #ipv6 only devices and allow them a way to connect to legacy (ipv4) internet sites. https://sgryphon.gamertheory.net/2022/12/running-nat64-in-a-dual-stack-network/
-
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...
-
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.