Posted: 2026-03-15
On the SporeStack side of things, I host a Monero node on Debian, on Ullr. I'd love to use OpenBSD, but OpenBSD+Monero does not mesh particularly well for a number of reasons.
This morning, I found that the Monero node had been down for a while. It turns out that apt-daily ran and reloaded services to the point of the interface losing its IP.
The good news is that otherwise it's been quite stable -- I don't know of anyone else using Debian on VMM like this. But the bad news is that I've been deploying Debian VPSs in the same manner, using ifupdown.
It seems like I should modernize and use whatever native systemd networking functionality there is these days. ifupdown is considered quite legacy at this point, even if I prefer working with it.
I figure some of you may also be impacted. Fortunately, you can use the serial console to remedy this. Some will also opt to not run apt-daily and instead do it manually. But either way, I clearly didn't provision this in the most bulletproof manner.
I have a new model for Debian network configuration, using systemd. I expect this will be more stable.
First, we have to remove /etc/netplan/* -- otherwise it won't work.
Now, a configuration example for 2602:f5ef:0:ff01::/64:
debian-guest# cat /etc/systemd/network/static.network [Match] Name = enp0s2 [Network] Address=2602:f5ef:0:ff01::1/64 Gateway=2602:f5ef:0:ff01:: DNS=2602:f5ef::1:0
Can reboot or networkctl reload to get this going, but you'll want to remove ifupdown if converting. And probably do this over serial console, while expecting some network downtime to be on the safe side.