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

If you want (or in my case have too) test some stuff with SLES and network equipment, you just can add a SLES container to your ContainerLab lab:

name: suse-lab

topology:
    nodes:
       suse:
         image: registry.suse.com/suse/sle15:latest
         kind: linux

One clab deploy later and you can access your SLES container:

root@clab:~/suse-lab# docker exec -ti clab-suse-suse bash
suse:/ # uname -a
Linux suse 6.1.0-40-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.153-1 (2025-09-20) x86_64 x86_64 x86_64 GNU/Linux