Blog/2026-01-03/IPv6 Seems Preferred
I saw a headline on HN today and decided to go and see if I had IPv6 connectivity. I used test-ipv6.com to see if I was on IPv6. I was surprised to see that I was on IPv4 only. I recall that dual-stack networks always have problems, so it wasn't surprising that I'd set it up this way.
But you have to grow up some time so I popped into my router, turned on IPv6 with DHCP6/SLAAC and after a few minutes (it took a surprisingly long time) I had an IPv6 address! Browsing the Internet seemed fine and test-ipv6 gave me the screenshot you see above.
But what weirdly happened is that I had some trouble with this blog. This funny thing happened because IPv6 is preferred by many tools apparently. Notably this meant that my IP-gated Cloudflare access was no longer valid since I was no longer contacting from my IPv4 but from my brand new IPv6.
Unfortunately, I wasn't quite doing these things one after the other, so I completely forgot about the IPv6 thing moments after I'd done it and so I was baffled when I went to search my blog for something and found that it wasn't working well.
I even went to the degree of rolling my credentials before I realized that I had IP-gated them. I am very surprised by my past self for having been this careful with my wiki storage. My site backups and everything go there. I would have expected that I'd have pushed it without an IP gate just for simplicity.
Of course, with IPv6 my ethernet interface on the server had two different `inet6` addresses (one internal and one globally routable). Honestly, a smarter man wouldn't have kicked this off before he was sure his firewall rules and routing tables were all sensible.
