carzian
That's not an earwig, this is an earwig
That's definitely something to be aware of, but the vdev expansion feature was mergered and will be released probably this year.
Additionally, it looks like the authors main gripe is the current way to expand is to add more vdevs. If you plan this out ahead of time then adding more vdevs incrementally isn't an issue, you just need to buy enough drives for a vdev. In homelab use this might an issue, but if OP is planning on a 40 drive setup then needing to buy drives in groups of 2-3 instead of individually shouldn't be a huge deal.
You need to research raid 1,6,10 and zfs first. Make an informed decision and go from there. You're basing the number of drives off of (uninformed) assumptions and that's going to drive all of your decisions the wrong way. Start with figuring out your target storage amount and how many drive failures you can tolerate.
Kinda has been. I did my iPod like this 2ish years ago
I've been using migadu and its been great so far
Ah ok. I've done opnsense and pfsense both virtualized in proxmox and on bare metal. I've done the setup both at two work places now and at home. I vastly prefer bare metal. Managing it in a VM is a pain. The nic pass through is fine, but it complicates configuration and troubleshooting. If you're not getting the speeds you want then there's now two systems to troubleshoot instead of one. Additionally, now you need to worry about keeping your hypervisor up and running in addition to the firewall. This makes updates and other maintance more difficult. Hypervisors do provide snapshots, but opnsense is easy enough to back up that it's not really a compelling argument.
My two cents is get the right equipment for the firewall and run bare metal. Having more CPU is great if you want to do intrusion detection, DNS filtering, vpns, etc. on the firewall. Don't feel like you need to hypervisor everything
So you're planning to reuse the same hardware that the firewall is running on now, by installing a hypervisor and then only running opnsense in that?
Downloaded from the KDE store
The command was rm -rf $pathvariable
Bug in the code caused the path to be root. Wasn't explicitly malicious
Did you expose your router login page to the open internet? How'd they get access? Why are you chmoding anything to be 777?
Yeah that's the one I meant. Damn, that's too bad