Admiral Patrick

I’m surprisingly level-headed for being a walking knot of anxiety.

Ask me anything.

I also develop Tesseract UI for Lemmy/Sublinks

  • 1 Post
  • 34 Comments
Joined 1 year ago
cake
Cake day: June 6th, 2023

help-circle













  • The barracuda I have is basically an x64 board in a 1U half-depth case with two extra network adapters (3 total including the onboard one). I have two of them: one’s running OpenWRT (my router) and the other vanilla Debian.

    So if my router one dies, I can just either pull the drive from it or restore a config backup to another suitable PC that has two NICs (or promote the second unit I have).

    The config in openwrt is abstracted. So if the hardware and NICs are totally different, you might need to reconfigure the device names in the config so they’re referencing the right NICs, but everything else should “just work” (e.g. WAN and LAN are just arbitrary labels).


  • If going the route of a backup solution, is it feasible to install OpenWRT on all of my devices, with the expectation that I can do some sort of automated backups of all settings and configurations, and restore in case of a router dying?

    That’s what I do. Every device runs OpenWRT except my ONT. Backing up is just a cron script that calls each one and pulls the config.

    For my router, I ended up buying an old Barracuda LoadBalancer 340 and installing OpenWRT (it’s an x86 device so it was super easy). It’s a little over-powered for a router, but the price was right. It’s got more than enough spare resources to run some extra stuff, including Docker, so I’m probably going to throw my PiHole container on there since I haven’t been impressed with AdGuard Home (which is available in the repos).

    And if you go for an old Barracuda unit like I did, the default BIOS password is bcndk1


  • Analog TV were a lot more susceptible to electromagnetic interference (EMI) and would go all fuzzy.

    Old vacuum cleaners had motors that put out a lot of EMI, so every time someone in the house would run the vacuum the TV would start acting up. (Wasn’t just vacuum cleaners: any appliance with a big motor could, but they were usually far enough away from the TV to not be an issue)

    Better shielding on appliances and the switch to digital/LCD TVs that weren’t susceptible to that form of interference all but made that problem disappear.





  • Wouldn’t restoring from such a backup be equivalent to kill -9 or pulling the cable and restarting the service?

    Disclaimer: Not familiar with Immich, but this is what I’ve experienced generally.

    AFAIK, effectively yes. The only thing you might lose is anything in memory that hasn’t been written to disk at the time the snapshot was taken (which is still effectively equivalent to kill -9).

    At work, we use Veeam which is snapshot based, and database server restores (or spinning up a test DB based off of production) work just fine. That said, we still take scheduled dumps/backups of the database servers just to have known-good states to roll back to if ever the need arises.