Yes! Qsl cards are very much still alive and well. Some traditions will never die. The special event stations are fun to get cards from.

Super cool anecdote on the telescope thing, I've never heard of that.

I hope you get back on the radio, it's a great hobby. It's a nice stress relief outlet for me these days too.

Love to hear things like that! When I first got licensed the solar cycle was utter trash. We're past the peak now, but band conditions are still pretty good generally. A few watts and a wire will still get you somewhere with CW and some other forward error corrected modes (like FT8). I have a lot of fun with the digital stuff like AREDN, but it's definitely a different ball game and the old school SSB-based radio still has its place in my heart.

The OIDC settings in the Authelia config reference were the most nebulous to me, but they weren't entirely stumping. The hard part was interpreting whether my errors stemmed from an issue on the client application side or on the Authelia side.

I would imagine you could likely extend the config snippets from my post to work in your situation with a few tweaks. The big lift, the OIDC provider is covered, so I'd be curious to hear what else you have to tweak!

Great question, I've asked myself the same thing.

First, in my opinion they serve to achieve different things. While openwrt is a firewall, it'd a simple zone based firewall and it designed primarily as router firmware, not firewall software.

Opnsense is BSD based, openwrt is Linux based. Those both haves pros and cons. BSD has serious pedigree in the networking world. Juniper switches are still based on BSD even. Openwrt gets the Linux traffic shaping goodies like cake though.

I chose openwrt because it's more suited to my environment, where I have 10 VLANs, a 10G fiber core, and want IDS/IPS. Openwrt is meant to be lighter weight, but is less feature-full.

No worries, and I'll accept criticism too, that's how you improve.

Anyway, this is effectively giving you tailscale, a remote access mesh VPN solution, but with total control and ownership of the control plane server, instead of relying on the opaque tailscale owned and controlled infra. I touched on it briefly again the 'DERP Config' section of part 2: https://roguesecurity.dev/blog/headscale-quadlet-part2#DERP%20Config

No, it's not you, the XML file isn't including post content yet. I wasn't sure how to do that, so figured I'd start with the simple thing of generating a list from the posts manifest for the time being. This would at least show you a link for when a new post is up, but you're right there's no content yet. When I have a bit more time I'll research how can I dynamically add the entire post content.

Great question. I tried to very briefly touch on it in the post. The bottom line is that its benefits are there mostly for rootless podman, which I've chosen not to implement here (yet). You can also configure it so that the socket is always active and that will then trigger the service associated with it, so that you save on resources when the service isn't needed. However, I didn't want to do that as it would likely increase page load time for readers.

The other poster here is correct, this is just an account of my journey through self hosting traefik, and ultimately headscale, without the hurdles along the way. I tried to include a few links to unclear terms along the way in the narrative, maybe those would help you figure things out. Unfortunately I can't write for an audience of everyone, but hopefully you can still gain some value or learn some new things! Thank you for the feedback.

Potentially, but precision is important, especially if you're going to make sweeping claims about a topic, acting as an authority.

Sure, but no one asked about studies from a specific country, we just got an unsolicited "tut tut" for no reason. I can live in Germany and read Canadian articles all I want. This particular poster just doesn't have an open mind about the world.