Windows CLAT Enters Private Preview: A Milestone for IPv6 Adoption
ipv6
#IPv6 was defined in RFC1883 in December of 1995.
That's right, IPv6 is now *30* frickin' years old. I've spent at least 25 of those yelling at people, companies, service providers, and many engineers who really should know better that they need to enable it.
Doesn't look like 2026 is going to change that. Le sigh.
#SpectrumInternet did maintenance during the middle of the night. It did not succeed, and will be rescheduled. But it came back with only ipv4 ip for me to nat. My decade+ of #IPv6 access via them stopped working, and support didn’t help for third party routers.
Boo.
If anyone would be willing to click this link and tell me if it worked for you, I'd be ever so grateful.
Did you every ask yourself whether your #Web thingy is ready for an #IPv6-only audience?
This question is surprisingly hard to answer as one has to account for resources dynamically loaded by JS and DNS dependencies. As a small step within #SAP 's journey to become IPv6-only ready, I built an #OpenSource tool that helps answering this question.
You can try out the IPv6 Web Resource Checker at https://webres6.dev.sap/ or fork it on https://github.com/SAP/webres6/
Let's see who finds surprising scores
I’m genuinely confuzzled: why is #ipv6 such a basket case in implementations at this very late date? When I have network issues, it seems to mostly come down to ipv6 being a right nuisance. (Yes, or how it is handled, but…)
Now my #IPv6 only network has IPv6 to IPv4 egress using DNS64 in #unbound and an af-to rule for 64:FF9B::/96. I just need to stand up an IPv6 only NGINX reverse proxy and the whole network will have native IPv6 and IPv4 access to the internet.
The configuration is very simple and once in place is set and forget.
Do not roll out IPv4 for any new deployments. Also think about migrating away from dual stack.
#OpenBSD
The configuration is very simple and once in place is set and forget.
Do not roll out IPv4 for any new deployments. Also think about migrating away from dual stack.
#OpenBSD
What will we all grouse about once GitHub is available on #IPv6?
So, I have been exploring #NNCP lately, and have it kind of sort of working...
But I struggle with a couple things:
How do you support multiple ip addresses from nncp-daemon?
https://nncp.mirrors.quux.org/nncp_002ddaemon.html#index-nncp_002ddaemon
Passing the -bind argument multiple times seems to be a last-argument-wins situation. It is unclear if wildcards work, if any. I have both #IPv4 and #IPv6 addresses, as well as multiples of each...
Run the daemon multiple times listening on different ports seems kind of excessive...
Okay, I think the time is finally here:
Please share / boots if you think this is a good idea.
And yes, the image is AI generated. I'm not an artist.
Edited 100d ago
Hello #Fosstodon! Our instance now supports both IPv4 and #IPv6! This should also include federation with IPv6-only instances. This has been our most requested feature on Fosstodon, so we’re super excited to add this support to our community.
Edited 32d ago
For the first time in my life, my home internet is faster than the connection on my datacenter servers. For once, the bottleneck isn't here, it's there.
Meaning, I can self-host stuff right here at the same speed as over there.
And I already have a couple of ideas on WHAT to host, on top of what I'm already running (and more efficient backups, obviously).
It's just a shame about the quality of the installation work. Seriously, unbelievable. Outside, the fiber cable wasn't even properly secured; it's just dangling off the wall with a couple of zip ties in the most pathetic way. If someone walks by on the inner pavement, they could easily snap it.
I'll have to take some time and try to fix it myself... but overall, the outcome is still extremely positive.
And finally, I have native IPv6, without needing any more Tunnel Brokers.