What I’m reading is that you want site-to-site connectivity. Wireguard + possibly dynamic DNS makes this pretty easy (assuming you can open ports and configure NAT at your sites). Or you could set up some other VPN solution like OpenVPN.

There’s also tailscale (a paid service) for facilitating the wireguard setup, NAT traversal and relaying. headscale is a self hosted solution that aims to provide something similar (but more limited in scope).

You can use man <command> (in this case man cut) to read a program’s manual page. Appending --help (without any other arguments will often produce at least a short description of the program and list the available options.

I’m also using Caddy with desec and get the same result when adding a new subdomain. It fixes itself after a while though (10+ minutes). Maybe try waiting a little longer.

I’m also using caddy with desec.io. When first triggering the challenge for an entry, it can fail a couple of times. I think it just takes a while for the DNS entry to be available.

Another thing that I’ve experienced is that I can’t use wildcard subdomain entries. My guess is that it’s somehow because I only have public IPv6 addresses (but I don’t remember the details). I have configured an internal DNS with the wildcard entry since I’m only ever connecting to that host via wireguard from outside my network. For the host itself I’ve created a regular AAAA record.

kmail is in the arch repository (in extra), the package is called kmail.

I know it sounds dumb, but lying still and thinking the same word over and over seems to help me if nothing else does the trick. If you notice yourself thinking something different just get back to it.

The right can’t meme

Kein Kommentar zum Artikel, aber die AfD hatte 2021 30100 Mitglieder vs. 18000 Graue Wölfe.

AfD

Graue Wölfe, 2017

Graue Wölfe, 2021

Fuck character limits for names. Looking at you, ABAP.

• For your first point you’d probably want to investigate why your system doesn’t suspend or what exactly is going on. You could check logind.conf, specifically the HandleLidSwitch* keys. Otherwise, your lid switch should have a corresponding /dev/input/ event that you could maybe listen to or something.

• I can’t offer much input on your second point. I think unplugging the audio jack should probably trigger a udev event that you could write a rule for. No idea about wireplumber though.