Are you running an #ipv6 only network of any kind? If so, what's on that network? Why is it ipv6 only? How's it going?

This question was prompted by watching the latest IPv6 Buzz Podcast titled, "Are We Stuck With Dual-Stack Forever?" ( https://packetpushers.net/podcasts/ipv6-buzz/ipb143-are-we-stuck-with-dual-stack-forever/ )

I am running a few IPv6 only networks. Mainly being used as management networks for switches, host controllers, etc.

I could switch some wifi networks over to #ipv6mostly if Epson's iProjection would work over NAT64 or IPv6 :(

IPB143: Are We Stuck With Dual-Stack Forever? | Packet Pushers

An IPv4 and IPv6 dual-stack approach can smooth the transition from one protocol to the other because organizations can get comfortable with IPv6 without having to make a hard cutover. However, they may get so comfortable that they never fully commit. Are we stuck with dual-stack forever?

@doachs My homelab blade server sits on an #IPv6only network, so that I can build experience with #IPv6 #k8s. Later on, I'll add #MaaS management, which will probably need PXE over IPv6. This network is routed, and does have #NAT64, which I consider distinct from dual-stack operations.

This setup has led to all sorts of edge cases, like GitHub needed to build containers, or CLAT to accommodate legacy IP apps. Overall, I consider it Continuing Education for networking and server management.

@doachs on my home setup I have a discrete single stack network, with DNS64 and NAT64, for experimenting. Most everything works these days, even including Airplay and Chromecast to v4-only devices on the dual stack side of the network, via the NAT64 layer and with some mDNS shenanigans. The ones that I'm still stuck with are some Reolink security cameras from their Android app, and a weird issue where trying to go IPv6-mostly seemed to bust "Messenger Kids" from an Android device. I am hopeful both of those might be solved once we get PREF64 in a mainline radvd release, but that's somewhat guessing from the symptoms of how things seemed to interact with Android and 464XLAT attempts.

🤞

@doachs My last org is mysteriously full of #IPv6-only networks. I think I had seven NAT64 clusters? All numbered with GUA space, so I could use any of them, at will.

These days, all I've got is labs — both at home and at work — and a few external VMs here and there, like from @beasts.

I'll get production IPv6 at my day job... sooner or later. 😀