42 Followers
241 Following
124 Posts

🇨🇭 |   
Breaking servers for a living
Enthusiastic nerd who never stops learning

Just a random person who is interested in security and privacy.

Websitehttps://www.schwitzd.me/
Githubhttps://github.com/Schwitzd

Playing again with #DNS settings on my #archlinux. This time I decided to use #systemd-resolved to benefit of #quad9 with #dot

#linux #networking #homelab
https://www.schwitzd.me/posts/secure-dns-networkd-resolved/

Secure DNS Networkd Resolved

This article will be very similar to Integrate Dnscrypt-proxy with a Home DNS Server, with the main difference that instead of using Dnscrypt-proxy to forward DNS queries to your preferred DoH nameserver, I will use systemd-resolved. At the moment, systemd-resolved only supports DoT (DNS over TLS). Support for DoH is still under development (issue #8639). Configure systemd-resolved Make sure it’s running and that /etc/resolv.conf points to it. sudo systemctl enable --now systemd-resolved Symlink /etc/resolv.conf to the stub resolver:

Schwitzd

My latest blog post is talking about how I have configured a #tunnelbroker on my #mikrotik thanks to #route64
Now I'm a happy owner of a #ipv6 subnet

#networking #homelab #selfhosted #wireguard #vpn #cgnat

https://www.schwitzd.me/posts/mikrotik-tunnelbroker-with-route64/

Mikrotik - Tunnelbroker with Route64

For learning purposes, I started looking into IPv6. First, I enabled a Unique local address subnet to leverage K3s dual-stack on my Home Cluster. Then I thought it would be cool to be able to connect to my home from abroad, so I started investigating VPNs. It is at this point that I discovered that my ISP currently is only offering IPv4 behind CGNAT for mobile devices (My Mikrotik connects to internet over LTE. Surfing the web I learned about tunnel broker is a service that provides IPv6 connectivity over an existing IPv4-only internet connection by encapsulating IPv6 traffic inside IPv4 packets.

Schwitzd

My home cluster uses #Longhorn for persistent storage, but I ran into messy startup issues caused by DNS resolution failures. Here's how I fixed it #Kubernetes #Homelab #DevOps #SelfHosting #CloudNative #dns #k3s

https://www.schwitzd.me/posts/troubleshooting-longhorn-slow-startup/

Troubleshooting Longhorn Slow Startup

In my K3s home cluster, I use Longhorn as the storage engine for my stateful workloads. Since I’m just starting out and shutting down the cluster every day (to safe my power bill), I’ve noticed that Longhorn takes a long time to be ready, with a messy startup involving a lot of errors and pods going into the CrashLoopBackOff state. Spoiler: It’s always DNS :) Troubleshooting I decided to take a look, so I began my troubleshooting journey by analyzing one of the affected pods.

Schwitzd

Finally switched from iptables to nftables on my Docker setup.
Had to wrestle a bit with bridge networks and rules, but it’s working now.
Wrote down the steps here 👉 https://www.schwitzd.me/posts/from-iptables-to-nftables-with-docker/

#nftables #iptables #docker #linux #selfhosting #devops #firewall #networking

From iptables to nftables with Docker

This blog post was initially intended to explain how to migrate from iptables to nftables — there are plenty of similar posts all over the internet. However, I soon realised that I was also running Docker on my laptop, which still does not natively support nftables at the time of writing. I therefore decided to write a dual-aim article: switching to nftables and allowing Docker containers to access the network. Disable iptables To fully transition to nftables and prevent conflicts, it’s important to stop and disable the legacy iptables services. You can do this with the following commands:

Schwitzd

Just published a post on my journey into #SelfHosting: building a #K3s home cluster with #Terraform, #Ansible, and some delightfully evil shutdown logic to save power without breaking anything.
https://www.schwitzd.me/posts/home-k3s-cluster-my-journey-into-self-hosting-automation/

#HomeLab #Kubernetes #GitOps #InfrastructureAsCode #DevOps #ArgoCD #Longhorn #linux #devops #raspberrypi

Home K3s Cluster: My Journey Into Self-Hosting & Automation

Why I Did It At first, this was a learning project. I wanted to understand the real nuts and bolts of Kubernetes — not just on paper, but on actual, bare-metal hardware in my home. But over time, it became something more. It became my platform — the place where I host the things I care about, where I experiment, where I break things and fix them again. What I Wanted To learn how things really work under the hood To automate everything — no clicking, no guesswork To host my own services with security and flexibility in mind To power things down when I don’t need them, and boot them up instantly when I do What I Built The stack is simple but powerful:

Schwitzd
I’ve been thinking about what it would look like if Oracle bought TikTok, but I am not sure if they will go with a per device or per core licensing model

Have you had that "Upcoming price change for your Microsoft 365 subscription" email yet? They want to charge you an extra 50%ish for AI features, and they do *not* make it easy to find the way to turn it off. It took me minutes of searching - this is a particularly evil dark pattern.

"Switch plan" just lets you pick between annual and monthly billing. You want "Turn off recurring billing" and then "Current subscription without AI".

You're welcome. Please boost for others.

Charging a device seems an easy task… but it’s definitely not. There are many technologies behind it that you can benefit from if you want to charge smart!

What I understood is: USB Power Delivery (PD) is a universal standard supporting up to 240W (PD 3.1), ideal for high-power devices. Qualcomm Quick Charge (QC) focuses on fast, efficient charging for Qualcomm-based devices. Meanwhile, Samsung relies on Adaptive Fast Charging (AFC).

But here's the catch: to take full advantage of these technologies, you need a good cable, but also a good charger. Don’t buy cheap cables or rely on the included charger—it might not support the necessary technologies. Not all cables or chargers can handle the high power or fast charging speeds required by PD, QC, or AFC.

Make sure both your cable and charger are rated for the technology you're using!

#FastCharging #usb #smartphone #TechTips

#TIL the power of yay -Rns <package> in Arch-based systems! 🎯

This command removes a package (-R), along with its unused dependencies (-n), and its configuration files (-s), ensuring a clean system. ✨ Always review before running! #Linux #ArchLinux #techtips #yay

Today is the day. Welcome to THE charger!

USB-C is officially the common standard for charging electronic devices in the EU.

This means:

🔌The same charger for all new phones, tablets and cameras
⚡ Harmonised fast-charging technology
🔄 Reduced e-waste
🛑 No more “Sorry, I don’t have the right cable”

One charger to rule them all.

#SingleMarket #DigitalEU