Windows CLAT Enters Private Preview: A Milestone for IPv6 Adoption
ipv6
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
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...