First, a hardware question. I’m looking for a computer to use as a… router? Louis calls it a router but it’s a computer that is upstream of my whole network and has two ethernet ports. And suggestions on this? Ideal amount or RAM? Ideal processor/speed? I have fiber internet, 10 gbps up and 10 gbps down, so I’m willing to spend a little more on higher bandwidth components. I’m assuming I won’t need a GPU.
Anyways, has anyone had a chance to look at his guide? It’s accompanied by two youtube videos that are about 7 hours each.
I don’t expect to do everything in his guide. I’d like to be able to VPN into my home network and SSH into some of my projects, use Immich, check out Plex or similar, and set up a NAS. Maybe other stuff after that but those are my main interests.
Any advice/links for a beginner are more than welcome.
Edit: thanks for all the info, lots of good stuff here. OpenWRT seems to be the most frequently recommended thing here so I’m looking into that now. Unfortunately my current router/AP (Asus AX6600) is not supported. I was hoping to not have to replace it, it was kinda pricey, I got it when I upgraded to fiber since it can do 6.6gbps. I’m currently looking into devices I can put upstream of my current hardware but I might have to bite the bullet and replace it.
Edit 2: This is looking pretty good right now.
You got the idea from here, right? :D
I’m not sure if you ever made your way to following through with this… But the three node system isn’t a bad starting point. However, here’s how I would approach it (similar to how I actually got my start in homelabs and how I do things now)
1 system for your router (looks like you picked a Qotom unit, those are decent), 8-16 gb ram
1 system for proxmox virtualization… run all your services in LXC’s or Virtual machines, as much ram as you can get a get for your system
And 1 system dedicated to storage (truenas or unraid), 32gb ECC ram (personal preference but not necessarily needed even with zfs for home use)
I’d start at https://reddit.com/r/homelab … but since we’re on Lemmy, I’d rather suggest posting on [email protected] (new, but looking to gain traction)
Just kinda flipped through his guide. It’s a bit dated on knowledge and techniques, even for beginners.
You don’t need a computer for a router. Get a router that ships with OpenWRT and start there. GL.iNet makes good and affordable stuff. Use that for your ad blocking, VPN, and so on to get started.
I’d just skip OpenVPN altogether and get started with Wireguard or Headscale/Tailscale.
If you want to run other heavier services, start out with a low-power minipc until you’re settled on what your needs or limitations are. You can get a very capable AMD minipc for $250-300, or an n100 low-power for a bit cheaper. Check out Minisforum units for this. Reliable, good price, and solid warranty.
If you deal in heavy storage, maybe consider adding a NAS to the mix, but maybe that’s a further steps. OpenWRT is a good starting point just to get your basic network services and remote access up, then just move on from there.
A good and fun starting point for some people is setting up Home Assistant on a minipc or Raspberry Pi (honestly, the costs of Pi boards now is insane. Might be good just to get the minipc).
To add to this, don’t buy a server at all, upgrade your desktop! Then use the desktop as a server. Then recycle every desktop for the rest of your life into the new server. Been working for me for decades.
Heh yeah same. Add in a couple of old pis and that is my “infrastructure”.
I’d just skip OpenVPN altogether and get started with Wireguard or Headscale/Tailscale.
This one was huge for me. OpenVPN is pretty heavy with CPU overhead, where as wireguard is almost free. I was getting throttled due to the overhead of OpenVPN and roasting the CPU on my Netgear R6350 (it’s what I had lying around). With wireguard I get nearly the same speeds as without a VPN and my loads are very reasonable.
Also with weaker routers like mine, be wary of trying to use QoS, this will probably not help network congestion and instead become a bottleneck (like it did for me). This is where a beefy dedicated router really shines.
First, thanks everyone for all the info, glad I posted. It’s a lot to go through.
OpenWRT is the most frequently recommended thing here, and my router is not supported. I somewhat recently purchased my router (Asus AX6600) when I switched to fiber due to its high bandwidth and I’d prefer to not replace it. I’ll look around and see what options I have for putting a separate device upstream of my current hardware and if that doesn’t work out then maybe I’ll replace my current router.
I see that you can install openwrt on a switch. Would it make sense to put a switch with openwrt upstream of my current router/AP?
Edit: dang there’s only 1 switch supported by openwrt that has 10 gbps ports (ZyXEL XGS1250-12)
Gl.iNet is a great value router, but if you want to do anything really interesting, it won’t do.
I have Slate AX chugging along, and have been eyeing teklager boxes to do actual routing, with slate as an access point.
This is a beginner. I wouldn’t try to overcomplicate it.
I wouldn’t trust his guides personally. He has some hot takes and more importantly he isn’t someone who really knows the Homelab/self hosting landscape.
If you are looking for guides I would find channels that have done series on whatever you are interested in there is plenty of quality material.
To start off here is what I would do.
First, get a wireless router that is capable of running OpenWRT and then get a switch to accompany it.
Next go to eBay and buy 3 used workstations. They don’t need to be fancy and you can always upgrade them later. You need 3 for later.
Next find some storage. You can find decent Sata SSDs for pretty cheap. If you are looking to store something bigger like a movie collection also pickup some larger drives. With the extra drives make sure you buy a sata or SAS pcie card. This is because you need a dedicated controller to passthough to a VM.
Once you have all that you can start installing Proxmox. You probably want a raid 1 configuration so that you can replace a disk without downtime. The reason I say three devices is because you need 3 machines to get consensus in the cluster. When consensus is lost affected devices go into what is called fencing which is where it freezes all VMs and operations to prevent split brain from happening.
Technically this is probably a bit overkill but I like having a solid base for experimentation and flexibility. Doing it right from the get go will mean that you have more power down the road.
For actually hosting stuff I would use docker compose inside a VM.
Any advice/links for a beginner
you can start installing Proxmox
🤔
Proxmox is a great starting point for self hosting. You don’t need advanced features to start, and you can easily create VMs and containers.
Yeah is guide is pretty useful! i went with setting up wireguard instead of openvpn. For a while now ive been self hosting alot of my stuff, SearXNG with gluetun tunneling, minecraft server for me and the boys and a Samba Share instead of paying for some dopey cloud storage. Ive gotten ZFS running in a 1tb z1 pool for my containers and plan to add a 10tb Z2 pool for long term storage and backups. i chose to do it in NixOS instead of debian or ubuntu, just because im a little bit of a nut for immutability.
its actually kinda funny i just left a post asking for help setting up wiregaurd server on c/selfhosted and referenced louis’s guide! Also i gotta add thats EPIC you got 10gbps internet, i went with a glinet flint 2 for my router. Because it runs openwrt under the hood, i personally like openwrt alot. there are people that swear by pfsense or opensense because of the bsd network stack, is very well maintained and secure as alot of commercial products like switches and firewalls run pfsense under the hood. for security and vlans pfsense would probably be better from what i heard. But openwrt works pretty well aswell, and i ended up just going with the flint 2 because it has 2.5gb wan in and 1 2.5gb lan. which was more than enough more my measly 1-2gb internet.
Just glancing through that guide:
OPNsense instead of Pfsense, because pfsense is going to rugpull, it’s just a matter of time. I wouldn’t trust the twats that run it farther than I could throw them because they’re pretty silly people. Rossman suggests exactly this in the intro to the router section, he would change if he hadn’t been using it for a decade already. Unfortunately, a lot of this guide is focussed on how to do it via pfsense and if you’re brand new, you’re going to have to figure out how to do it in OPNsense yourself.
Wireguard/Tailscale instead of openvpn. Faster and way easier to set up. Don’t even try to set up a full LAN routed VPN, just use Tailscale for the services you want. And use it for everything and everyone instead of punching holes in the firewall.
He’s definitely right about mailcow; if you’re reading that guide for information, you are not a person that should be self-hosting email.
I would probably suggest just getting a Synology NAS or similar because it’s plug and play.
I have big regrets buying a WD MyCloud device.
It sucks. Massively sucks. I have it robot nightly or else it stops working.
Wish I’d started with a Synology.
Quite a few model years of Synology were stricken with a network transceiver issue where they would just stop talking randomly.
I have two WD-EX4’s and the six bay Synology, and none of them have the kind of uptime I get out of my unraid.
If you want something rock solid I would probably scratch build a box with truenas
Sounds like you need to back that thing up asap
The whole idea of self-hosted is to build something yourself and learn your way around some new technology or software. Plus building something yourself allows you to change and upgrade it down the path, while Synology doesn’t provide any of the sort.
To me, that’s the purpose of a “homelab” not the purpose of self hosting. There’s a lot of overlap, but they’re not quite the same. Homelab has a goal of learning, but just self hosting doesn’t need to.
