For a few weeks I had some strange errors with my self-hosted webmail, Snappymail. After working for some time it complained that it couldn't connect to tcp://mydomain.tld:143. My email clients worked, though. The situation got worse a few days ago when I updated the server and rebooted it.

My webmail is hosted in a systemd-nspawn system container. I use such containers for a lot of different services.

For debugging purposes I tried some telnet and openssl s_client stuff today but I've been on the wrong track with that. ping'ing from the webmail container already failed. There was something more fundamental amiss.

#systemd #networkd #nspawn #nft #selfhosted

Another day, another IPv6 question. I'm on a Hetzner cloud VM. I have a static IPv6 /64 subnet / prefix¹. The system uses systemd-networkd for network management.

My eth0 does not seem to receive any RA at all but I'd like to delegate the prefix downstream to a bridge interface br0 on the same host. I have an IPv6Prefix section on eth0 with the Prefix=…, Assign=yes and Token=static:::1. It works, eth0 gets the ::1 address for this prefix.

Is there a way for br0 to get this prefix too without eth0 joining the bridge? And to announce the prefix to any interfaces joining the bridge (e.g. LX system containers)?

¹ Is this the same? I have the impression these terms are used interchangeably with IPv6.

#ipv6 #systemd #networkd #systemdNetworkd

Okay, really scary systemd-networkd moment: I replaced a lot of the #networkd config files on my server with new ones, that create bonds, bridges, etc and even move the IP address I am connected to from one of the interfaces to a bridge and move the interface onto the bridge.

I prepared the OOB connection and entered `networkctl reload` with the expectation that I will break my config.

And 2 seconds later my prompt appeared again on my SSH session. I love it when stuff magically just works.😍