I have dual ISP connections at home due to the uptime requirements of working from the home office. It's nice sometimes to be able to connect back to the home office when I'm out (I've found various reasons over the years heh), and memorizing two ips is, well, twice as difficult as memorizing one ip.

The problem is, both my ISP uplinks are DHCP-assigned. They tend to be stable, but they could change at a moment's notice. And if working in tech has taught me anything, it's that...

Spent the better part of the night screwing around with installing OpenBSD on a Raspberry Pi 3 B+ (note the subtle extra character right at the end, there). It's irritating that a device can go from Version "3 B" to "3 B+" and so much changed. Spent a good bit of time goofing around with dtb files and trying to find the magic combination that would allow me to boot. Got close a few times, but the ethernet port refused to show up.

Ok, perhaps this is just an...

I was setting up smokeping in a docker container on a recently-repurposed machine on my home network, as I recently downsized from a Cisco 3560 core switch to two Ubiquiti US-8s (primary reasoning: the US-8 handles vlans like a champ, and I can run them both on my battery bank with a lighter wattage impact than the 3560). Smokeping was reporting some odd numbers which illustrates a quirk about switches/routers designed for management purposes, so I thought I'd write here about the effect and what...

user@host:~$ sudo reboot
[sudo] password for user:
Failed to start reboot.target: Connection timed out
See system logs and 'systemctl status reboot.target' for details.

Words cannot express how infuriating and depressing that error message is. Just turn the &$(&%^Y(#@ computer off!

Edit: It gets ever more obnoxious:

root@host:~# systemctl status reboot.target
Failed to get properties: Connection timed out
...

Had this problem after an ip change for my controller. I have an EdgeRouter Lite with 2 US-8's hanging off of eth1 and eth2, and for silly reasons I needed to move my controller laptop from one US-8 to the other. Once I did that, the US-8 it was previously attached to and the AP-AC-LR attached to the old US-8 showed up in "Disconnected" state in the controller software (eth1 and eth2 are not bridged, currently. If they were, it would have avoided this issue).

A cursory...