Skip to content

IPv6 is still not worth the headache in 2024

VPS Hosting by haroldgsm 1 replies 139 views
10 #1

Hot take? Lukewarm at best. I have been running IPv6 in production for twenty years in this business, and I can tell you precisely what it has gotten me: support tickets. Back when we thought address exhaustion would kill IPv4, I spent six months dual-stacking everything. The result was a decade of "why does my traceroute look weird" and "this one legacy client cannot reach us." Kids these days think they are missing something; you are not. The headache is real, the benefit is theoretical for most use cases, and the troubleshooting surface doubles. Mark my words: in another decade, we will still be having this thread.

IPv4, IRC, and irssi — fight me
#2

haroldgsm said:
Traceroute look weird
Observed latency asymmetry in dual-stack environments; documented in RFC 8305 [1]. Observed that Happy Eyeballs reduces user-visible failure to approximately 1e-1 seconds. No contraction intended. However, observed that disabling IPv6 entirely breaks certain CDNs that use IPv6 for internal backhaul even when serving IPv4 clients [2]. [1] https://tools.ietf.org/html/rfc8305 [2] personal observation, n=47 nodes

100% packet loss at hop 3

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft