A couple of days ago I watched a video on YouTube where, during a demo, the creator tried to download a file via wget. It didn’t work. When he tried curl, it worked (That was only a very tiny part of the video).

So why does curl work and wget not? My guess: broken IPv6 on the host. Happy-Eyeballs (HE) is defined in RFC8305 and is used to workaround broken IPv6 connections. It only works for HTTP(S). Basically if a target is dual-stacked a client supporting HE makes two connections to the target and then uses the better (as in working or faster) connection. So if IPv6 on your host is broken you won’t notice.

I had AI write a script to analyze Caddy logfiles to see the ratio between IPv4 and IPv6 for this blog.

IPv4: 58.51%
IPv6: 41.49%

Over the weekend I’ll work on some fail2ban rules to keep bots and (wordpress) junk out. Let’s see if this changes.

In a previous post I wrote that I started a gofundme to produce an IPv6 related tutorial series on YouTube, accompanied by blog posts, slides, labs and contributions to other projects like https://github.com/becarpenter/book6/

All videos will max. 20min, add free and I will reject any non relevant sponsoring.

Here are my ideas for the first 10 lessons (subject to change), not all off them strictly about IPv6, but also related topics like building your own lab, DNS, etc.

Based on another “IPv6 is bad” post on mastodon I diced it’s finally time:

https://gofund.me/49dd0f9c9

Fund me to produce an IPv6 related tutorial series on YouTube, accompanied by blog posts, slides, labs and contributions to other projects, e.g. https://github.com/becarpenter/book6/

It’s been a while but I just update the IPv6-Resources list on gitlab.

How to contribute

• create a merge / pull request (prefred)
• create an Issue
• mark commerical products, like books, training and tools
• mark links that are not in English