IPv6

TL;DR Deploy your own Forgejo runner in an IPv6-only Kubernetes cluster by patching the docker daemon.json 🚄 This post was supported by EC164 “Transalpin” and EC112 “Blauer Enzian” Why Codeberg/Forgejo? What are the actions for? Recently, I’ve started to migrate some of my git repositories from GitHub to Codeberg, which is a Forgejo instance, as I’m more comfortable with a community-driven Git & Development platform. Forgejo offers lots of features known from similar platforms (like PRs, Issues, and Actions), but obviously with limited resources (and sometimes features) due to the nature of the relatively young ecosystem. ...

TL;DR Using WireGuard with VRFs under systemd-networkd. The concept When using VPNs for all of your traffic, you usually have a “private” network part (inside VPN), and a public one (public/direct internet, not trusted), which needs separation. From a practical perspective, you might want to have a Linux-based router with an “inner” default network, transported by WireGuard tunnels, and an external network for the internet, over which the VPN data is transported. The Public routing domain shall be routed completely separated from the private routing domain, so no packets can leak between them. No Layer 2 is used, packets in both domains are isolated and shall be routed differently. ...

TL:DR How to add a warning banner to a web service, when a user visits via IPv4 User awareness for LegacyIP Recently, I got myself an IPv6-only network, and since then I’m figuring out how to design service connectivity for LegacyIP (also called IPv4). Using LegacyIP addresses in my own network is no option. My goal is to run IPv6-only services. To realise this, IPv6-Deployment must improve. As I am writing these lines, Google states roughly 50% of German requests are using IPv6. What about the other half? ...