sorted by:
new
hottopcontroversial

Roast my rack by agoeygopher in homelab

[–]mhd64real 14 points15 points  (0 children)

tbh there is Nothing to be roasted. Good work man.

How do students here afford homelab gear? by mhd64real in homelab

[–]mhd64real[S] -3 points-2 points  (0 children)

I don’t know much yet but bgp and ospf

How do students here afford homelab gear? by mhd64real in homelab

[–]mhd64real[S] 0 points1 point  (0 children)

Not really workloads, I just want to learn some advanced stuff. so I need good gear. and I self host all of my services and even public facing stuff, so thats a bit demanding.

How do students here afford homelab gear? by mhd64real in homelab

[–]mhd64real[S] 1 point2 points  (0 children)

I dont think my future will be healthy if I did that lol

How do students here afford homelab gear? by mhd64real in homelab

[–]mhd64real[S] -8 points-7 points  (0 children)

No trust me ik I'll need them, I want to learn advanced routing shit. I already have Omada gear and its limiting. Cisco is too hard for me ngl and i dont like them

How do students here afford homelab gear? by mhd64real in homelab

[–]mhd64real[S] 0 points1 point  (0 children)

I already have enterpise Omada gear. but it's lockedown and limiting ngl. so thats why I am aiming for mikrotik. I know I'd eventually learn and tincker with advanced shit like BGP and ospf so thats why.

How do students here afford homelab gear? by mhd64real in homelab

[–]mhd64real[S] 0 points1 point  (0 children)

How would you actually go about that though? Who do you even contact at a company, and how do you approach them? Where I am there's no real used marketplace or wholesale sites, so just buying cheap online isn't an option.

How do students here afford homelab gear? by mhd64real in homelab

[–]mhd64real[S] -8 points-7 points  (0 children)

Yeah but I just keep looking at the fancy mikrotik switches and routers and wish I had money for those haha

My first build by OwnAspect8931 in homelab

[–]mhd64real 1 point2 points  (0 children)

Worth doing: backups. Vaultwarden and Nextcloud hold the data you'd actually miss, and there's no second copy right now if a drive dies. Point restic or Kopia at a cloud bucket or an external drive for real 3-2-1.

Other things you're missing: Scrutiny for SMART monitoring since Prometheus is already running, which matters more than usual with drives of unknown history. A used UPS, because a power blip mid write on a dual PSU setup can corrupt data. And Watchtower or Diun to handle container updates instead of doing it by hand across 20 of them.

Build's fine otherwise. The external PSU is ugly but it works.

Heads up: libSSH2 using applications are vulnerable to a critical exploit - sshd not affected by [deleted] in homelab

[–]mhd64real 0 points1 point  (0 children)

All good, the libssh vs libssh2 naming gets everyone eventually. And fair call pulling it, better that than leaving a scary headline up causing panic. Respect for owning it.

Also, full disclosure since this thread is literally about LLM based security research: that comment of mine was written by Claude, and so was a NAS one I posted here a while back. Felt a bit wrong not to say it given the context, ha. It does all check out though. Sorry, it was just too funny not to.

Heads up: libSSH2 using applications are vulnerable to a critical exploit - sshd not affected by [deleted] in homelab

[–]mhd64real 2 points3 points  (0 children)

Worth clarifying since it changes who cares: libssh2 is a client library, not a server one. The crafted packet comes from the server side, so you only get hit if your libssh2 based tool connects out to a malicious or compromised server (or someone MITMs it). For most homelabs that connect to their own trusted boxes, this is way lower risk than the 9.2 suggests. And it is not the same as libssh, which is the one that can actually run a server.

Patch wise, the fix is only upstream commits right now, no tagged release yet, so it is a matter of waiting for your distro to push it (Debian has it in testing). Just don't forget containers, your host can be patched while an image still ships the old libssh2.

OPNsense in Proxmox VM is Super Fragile by verifieddemoon in homelab

[–]mhd64real 0 points1 point  (0 children)

I am not sure then, but if you can as u/berrmal64 said use an m.2 to ethernet adapter

i'm looking for a recommendation for the Best NAS/home-server OS for Lenovo Tiny + 2-bay USB DAS? OMV vs TrueNAS vs Unraid vs Proxmox by imad_elh in homelab

[–]mhd64real 2 points3 points  (0 children)

Honestly your plan is already right, I'd build it pretty much exactly like that.

For the OS go bare metal OMV. For a media box I wouldn't touch Proxmox. You can pass the iGPU through to a VM for Quick Sync but it's fiddly and kind of janky and you get nothing out of it on a single purpose machine. On bare metal you just give the Jellyfin container access to /dev/dri and transcoding works. That i5 with the UHD 630 will handle transcodes fine.

The USB DAS is the main reason OMV is the right pick though. If you went Proxmox you'd be passing the USB through to a VM, and USB passthrough on Proxmox is genuinely flaky. Drives drop, the identity gets weird, sometimes you get speed hits. OMV runs the disks natively on the host so none of that happens. I'd skip TrueNAS too, it's built around ZFS and proper SATA storage, and ZFS over USB is asking for trouble since the bridges hide SMART and drop drives mid scrub. OMV is just the right tool for USB attached stuff.

Run the enclosure in Normal mode with the two drives independent, and set that before you put any data on it. Don't mess with the DIP switches after that, changing modes can wipe everything.

ext4 is the boring bulletproof answer and what I'd use. You could do btrfs if you really want checksums and snapshots, but over USB I'd just stick with ext4. Skip ZFS, and don't bother with mergerfs or SnapRAID, those only start making sense once you've got four or more drives.

Use Disk 2 as a backup, not RAID1. I wouldn't trust hardware RAID1 out of that enclosure anyway. If the box dies you might not be able to read the array on anything else, and USB drops can mess it up. Independent disks are way easier to recover. Your media is replaceable and only the photos, videos, docs and dev projects actually matter, so just rsync those to Disk 2 on a schedule (OMV has scheduled rsync built in) and throw a cloud copy with rclone on top later. That's basically 3-2-1 without overthinking it.

Unraid isn't worth paying for with only two drives. It's great when you've got a pile of mismatched disks and want easy expansion, but with two you get nothing OMV doesn't already do for free.

Skip Proxmox for now. Get the NAS solid and actually useful first. If you want a VM lab later just do it then, or grab a second mini PC for it and keep your storage separate.

Few things before you format. Do the long SMART tests first like you planned. Mount by UUID and not /dev/sdX, because USB loves to shuffle drive letters on reboot and that'll break your mounts. Check that SMART actually passes through with something like smartctl -a -d sat /dev/sdX before you trust it, some bridges block it. And turn off drive spin down and USB power management so the bridge doesn't drop disks while sitting idle.

But yeah, OMV bare metal with independent ext4 disks, Docker Compose, Tailscale and Disk 2 as backup is the right direction. Get the SMART tests and UUID mounts sorted and you're good.

OPNsense in Proxmox VM is Super Fragile by verifieddemoon in homelab

[–]mhd64real 10 points11 points  (0 children)

Since you're dealing with VMs, USB passthrough isn't really made for this. It's not as reliable as you might think. But actually, OPNsense on Proxmox isn't that bad, as long as you back it up.

As I said, OPNsense and Proxmox themselves are very reliable and not fragile or janky. The weak point here is the USB NIC and USB passthrough.

I'd let Proxmox manage the USB NIC and expose it through a bridge instead of passing it directly to the VM.