• 0 Posts
  • 10 Comments
Joined 1 year ago
cake
Cake day: June 4th, 2025

help-circle
  • Cool thing with a lot of older “non-technical” users like that is they only need a browser and a way to print. Windows/Linux/Mac/Chromebook all end up doing the same thing for them.

    Put my pops on popos a few years ago and has been great for general computing. Still get the same support calls, generally to do with some website/logins type stuff. I think even medical imaging discs/downloads even work (the ones bundled with thr dicom viewer )

    ones I installed and never used

    Sounds like the same maintenance routine i have


  • Opnsense VM proxmox is how I’ve been set up for years now. Whatever you choose now will be a piece of cake to migrate later, either as VM backup/restore or opnsense’s, so don’t fret too much.

    I’d use the tiny PC if the 1 Gbps cards are good enough. “Up to 1.2Gbps” that’s pretty close. Reason for tiny PC is to keep internet in separate hardware than the rest. For me, limiting when I could do anything hardware related on the homeserver to when internet outages are OK was too much. I use a mini PC n100 for opnsense and pihole (so the core network stuff, routing firewall dhcp dns).

    Whichever hardware you’re on, I would have the wan nic on it’s own bridge in proxmox, cable straight to ISP. Opnsense VM gets a vnic on that bridge for wan. Then lan one is just like your other VMs on the lan/inside bridge. Same setup whichever box you end up on. And backup/restore the VM if you want to migrate or test and compare speeds on both. or explore HA and have both involved.

    To parent’s point about skipping the hypervisor: that works great too. Opnsense install on a new drive and restoring cfg backup is super quick, which would be one of the big benefits of using a VM. You can do a lot of add-on stuff in opnsense like adblocking, so possibly eliminate need for running those as side VMs on a “network box” like mine.

    If you’ve got the time and desire, test them all out. Once you get migrated to opnsense itll be easy to swap around




  • Another step is considering which things actually need to be an always on service, or how reachable it nerds to be. Reachability to limit Internet exposure, whether that’s pulling everything back behind VPN or just local/at home only. I was starting to look at which of those services even really need to be a service vs just some files on a NAS. Simple files and simple access not tied to apps that need troubleshooting, and probably lesser hardware requirement (compute/memory->power)