Some time ago I’ve tried to solve a ‘funny’ issue with PowerDNS. It refused to start on one of my backup VPS. After apt-get dist-upgrade, it first stopped to work with very meaningful ‘
Failed at step ADDRESS_FAMILIES‘ error. Well, I’ve managed to solve it somehow, but than another ‘funny’ problem popped out…
I encountered this problem again, so let’s write it down to avoid googling it.
PowerDNS fails to start with
pdns.service: Failed at step ADDRESS_FAMILIES spawning /usr/sbin/pdns_server: Invalid argument
- edit /lib/systemd/system/pdns.service
- comment out RestrictAddressFamilies
- comment out ProtectSystem=full
- possibly kill systemd-resolved
- systemctl daemon-reload
- ask yourself again, why are you using debian with systemd on server ? And why the hell it is starting services I’ve never configured to start ? Isn’t it time to switch to windows ? It seems more predictable to me…
I’ve hacked together and up-to-date version of Asuswrt Merlin firmware for oldie but goldie Asus RT-N16 router. Beware, this firmware is only intended for use by advanced users.
tinc is a great mesh Virtual Private Network daemon, with just one little glitch (and also little crypto problems ;-). I find its configuration really tedious and complicated compared to OpenVPN and its possibility to centrally assign IP addresses and push options to clients. I know, that’s the tax for being mesh, but wouldn’t it be great to configure your mesh network a bit centrally ?
Sometime it’s needed to selectively route specified IPs or networks via different interface – i.e. if you want to route private addresses over VPN (a.k.a split tunnel routing) or to route some public IPs over VPN to unblock some nationally restricted sites (Netflix). Here are simple scripts to achieve this.