Dan OachsJan 30, 2024

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?

Show threadJima 

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

Jan 30, 2024 at 7:15amWeb