Uh. OpnSense on bare metal can also do snapshots, if you set it up correctly…

And that’s the fault of whoever uses those hubs. You can use practically any zigbee hub you wish. Zigbee is zigbee.

You didn’t look very hard.

Cheap zigbee stuff exists everywhere. And zigbee is an open standard, so if it works, it will work until the equipment breaks.

The Linux kernel isn’t really much different between any distribution of Linux.

If it works on one, it works on the rest, in like 99% of cases.

The only real exception to that is custom distributions built specifically for a particular device or subset of devices.

In other words, for embedded devices, like phones, routers, TVs and such.

And those aren’t going to be running Ubuntu.

In my own experience, certain things should always be on their own dedicated machines.

My primary router/firewall is on bare metal for this very reason.

I do not want to worry about my home network being completely unusable by the rest of my family because I decided to tweak something on the server.

I could quite easily run OpnSense in a VM, and I do that, too. I run proxmox, and have OpnSense installed and configured to at least provide connectivity for most devices. (Long story short: I have several subnets in my home network, but my VM OpnSense setup does not, as I only had one extra interface on that equipment, so only devices on the primary network would work)

And tbh, that only exists because I did have a router die, and installed OpnSense into my proxmox server temporarily while awaiting new-to-me equipment.

I didn’t see a point in removing it. So it’s there, just not automatically started.

My reasons for keeping OpnSense on bare metal mirror yours. But additionally I don’t want my network to take a crap because my proxmox box goes down.

I constantly am tweaking that machine…

Lidarr + last.fm recommended list.

I have a few smart playlists set up that are each various genres of music. It’s not perfect, but it works well enough.

Not sure just how you want me to show it, but this how my music is, on the drive(s)

du -hd1 | grep Music

3.0T ./Music

I have about 85k tracks. :)

![](https://lemmy.world/pictrs/image/b11a6b02-a232-4c3f-bbcb-28e796cb97d2.png

See where it says “Files” ?

You’re complaining about a player feature, and blaming the server.

I use Symfonium and Navidrome, and I absolutely can browse my Navidrome library by folder if I wanted to.

I use navidrome. And what’s nice about it is, there are 3 people in my household, they can all access that. We all have our own favorite tracks saved in our preferred player, and we can still save a good chunk of them to our phones.

In my case, I have a random mood playlist of 200 tracks that gets updated every morning before I wake up, my phone app caches all 200 of them, so I can play them without network access.

You’ll know it when you find it. 🤣

I have over 3 TB of music. SD cards aren’t quite that big yet.

IPMI + BMC are wonderful things.

When people talk about CPU limitations on the rPi, they aren’t talking about just the actual processing portion of the machine. There are also a lot of other corners cut for basically all SBCs. Including bus width and throughput.

The problem is that when you use a software raid, like ZFS, or it’s precursors, you are using far more than the CPU. You’re also using the data bus between the CPU and the IO controller.

“CPU usage” indicators don’t really tell you how active your data buses are, but how active your CPU is, in having to process information.

Basically, it’s the difference between IO wait states, and CPU usage.

The Pi is absolutely a poor choice for input/output, period. Regardless of your “metrics” tell you, it’s data bus simply does not have the bandwidth necessary to control several hard drives at once with any sort of real world usability.

You’ve wasted your money on an entire ecosystem by trying to make it do something it wasn’t designed, nor has the capability, to do.

It’s bus limited, not necessarily CPU limited.

Get Oracle cloud free VPS. Create a VPN connection from your server to it.

Set up port forwarding from your VPS to your server. Connect to your server using your vps’ IPv4 address.

Done.

Works better than a proxy, for sure.

My folks had a tape backup system in the late 1990s. It used 250MB tapes.

They’ve been around for decades.