My Homelab Setup
arslan.io
arslan.io
Cool setup no doubt because unifi does make some good bang for your buck hardware that is low maintenance if you want to mostly just set it and forget it. And this looks like one of those set it and forget it control from a panel things.
But this is less lab and more network imo.
I used to push back against this, and I ended up getting really frustrated.
But then I realized that nobody else really cares, language changes, and I should just pay attention to other sources if I didn't like it.
At this point, to me, "homelab" means Plex, maybe some good organization of your stuff, and just enjoying setting something up that probably isn't really experimental. AKA production, but for the home.
I might be imagining it, but it seems like most people who are experimenting don't call it a homelab first, if they do at all. It's "the HA cluster I'm playing with" or "my AD setup for pentesting" or whatever.
In a home, having this kind of a setup is akin to installing appliances that can be set, forgot, and relied on more and more. Everything can have a fast connection, and if enough people work from home, etc, it can be really useful.
There's always ways to make do, and have failover, or backup internet, but in reality, it can be worth it to look at plug and play for home like this to not rely on anything.
Ubiquiti has taken it's lumps recently, but their stuff is still generally OK for home. Other providers like TP-Link with their OMADA setup are quite decent too, it's always possible to go full pfSense, or better yet, as an appliance, just buy a Netgate switch that can do a lot relatively for great bang for the buck.
I have recently used a Ubiquity Dream Machine Pro SE, and it's super decent for any small office or home setup. It just kind of runs, and you can reasonably run and segment a fair bit. It's too bad the new hardware took a step back in what the software allowed but it looks like they're adding the features each release little by little.
A lot of hardware for homelabs can increasingly get into issues with licensing, updates, etc. Once we are beyond 2.5 Gbit fibre into most homes, the jump to 10 Gig equipment and beyond and how to slice and dice it has fewer options.
I would today, not purchase any 1Gbit or 2.5Gbit fibre network hardware. Speeds are increasing, too fast. My homelab might have an older switch one day that an handle multiple 10gig fibre runs, both inside and maybe coming inside.
Having a part of a homelab that is like an appliance (largely set and forget), it can let you have more time to experiment with the experimental.
Production grade in a homelab can be possible too, where others might rely on it. Don't want that getting in the way of homelabbing.
If I see cable management, it just tells me that they spent more time doing that than labbing.
For commercial clients, we use the Unifi series and are very happy with it. I won't use Unifi for home because its strength is too high and I am very paranoid when it comes to signals blasting and penetrating more than a drywall. Wifi shouldn't be strong enough to be picked up outside of my house and I accomplish it with weak tplink per room mesh units.
I don't remember using more than 350 mbit data transfer over my ethernet since my internet speed is capped at 350 mbit. My NAS is connected to my SonicWall directly and can reach maximum read/write speeds (for cloud backups).
I'd invest that money in the stock market and make money instead. But I get it. A hobby is a hobby.
I started with cable, then moved to fiber, and now planning to move to 10Gbps fiber with sonic, and for sure I use any bandwidth I can.
At 1Gbps, I do saturate a lot of providers for things I do, but for the ones I don't, it's helpful.
I will subscribe to 10gbps sonic fiber soon, that's what prompted me to look into this. Unifi seems to cap wifi 7 at 2.5Gbps, however.
I give UI a +1 for overall quality/integration and being an American company, but TPLink seems also well praised recently. With Tapo Cameras etc they seem to be going in the steps of UI too.
I had two shopping lists written down, one for Unifi, one for TP-link. It was a combination of a couple of factors. It was actually a really tough decision, because they both seemed very good value for money. I wasn't factoring in cameras, just controller + switch + APs.
It was a combination of a couple of factors (this was in 2022):
- UI and integration
- Number of reviews and write-ups
- What I could find in stock
If I were doing it again today, I couldn't guarantee that my decision would be the same. It'd be a tough one...yet again.
Whenever I get the urge to go full on homelab like this, I remind myself that my poor wife will have to deal with the whole thing if I pass away. I’ve sort of settled on just having a single small home Linux server that backs up otherwise accessible cloud stuff that my wife can manage. I can still appreciate your setup though…
At least according to the disgruntled former employees that left sometime between the lifelogging wearable camera acquisition and the forced cloud/updates and the “massive” data breach.
What would be the 2024 version of how great UI was in 2014? Or what are your fellow hacker setups? Ideally something that does local first management, connection bonding, 10gbs, tailscale level of simplicity? I have the same setup as the author and uncomfortable with the Apple-ification of the product to something that looks pretty without meaningful root privileges.
TP-Link and omeda is probably an alternative, but after spending time trying to figure out what they offer and what their alternatives are for my needs I just give up with their confusing model numbers and half hearted explainations.
The problem I really have with Ubiquiti is when I look at their offerings and what I need I am immediately put into their Enterprise offerings and I am running 48 ports.
- closed source
- cloud connected
I just called it homelab, because I've seen people use the names interchangeable.
Happy to answer any questions not explained in the blog post.
We're building a house, moving from an apartment. I ensured that we get a fiber line to each room, and 2 to open spaces where I might want to extend wifi networks. Then CAT 6 cables to where cameras will be. I have a Nest wifi with 2 router extensions and a wireless one, so I've prioritised where I'll place those (and their eventual replacements).
My setup will be simpler, because I'm not really building a home lab (I agree with other comments that this isn't really a homelab). I just want to move noisy devices like a NAS and switches to the garage. My home office has space for a long rack if I desire one, but I think I'm going to make it a hybrid glass-door display cabinet that also houses the desktop so I don't hear fan noises.
This is a good write-up still because it's giving me ideas of what I might need for networking.
Fibre is cheap and you can get it cut to whatever lengths, and it’s somewhat future proofed.
Hell, there was probably a time where ethernet was too expensive to put into a house.
For example, I have some rooms with WiFi access points and things like scanners or Sonos speakers. Adding another PoE switch would be overkill.
I'd recommend cat6 that you can power if needed and fibre just where you think you'll need the speed.
Everyone's got what they're interested in; mine is definitely not radio voodoo.
And what's with the obsession with aesthetics? You spent a bunch of money on fancy cable management and patch panels, but you're still using a bunch of ugly, exposed cables. It's like you're trying to make a statement about how much money you have, rather than actually building a functional network.
And don't even get me started on the DNS settings. You're using a custom domain name for your Synology NAS, but you're still using DHCP to assign IP addresses. What's the point of having a custom domain name if you're just going to use a dynamic IP address?
I'm not trying to be mean-spirited, but this post just reeks of "I have a lot of money and I want to show it off". If you're actually interested in building a functional home lab, I'd be happy to offer some advice. But if you're just looking for a way to justify buying a bunch of expensive networking gear, then maybe you should just stick to playing with your toys.
1. Get a hardware firewall (opnsense/pfsene) and learn to use it (1-3 years)
2. Get a virtualization server and learn what the separation of concerns principle means (1-2 years); (this includes adding vlans)
3. Add the first Smart Home tools that are critical to you (e.g. monitoring of electricity consumption/production or automation of activity scenes for burglar defense) (6 months)
4. Work on a resilient backup solution. This includes offsite backups, so you will need to add a second server in a second house somewhere else. This _should_ come earlier, but you may have some backup solution in place already when starting at (1), so now is the time to do it properly (e.g. ZFS, automated syncoid pull-mode snapshots etc.) (1-2 years)
5. Try to improve individual pieces, maybe buy a larger rack, a UPS etc. (3 months)
6. At this time, you have a fully functioning Homelab. Now it is time to improve the look.. but doh, you have no time left anymore!
(above is basically my history.. started in 2017 and I am now after 7 years at stage (6), but otherwise overall pretty happy with my ugly looking setup)
VLAN are perhaps the most important aspect of a network, and honestly I would start with it: tag the ports, bonding if necessary, and figure out IPv6-PD and resolve topology for it all, so that downstream DNS is easily configurable.
Otherwise, I slightly agree that for the regular user, OpenWrt is simpler and less of a hassle than pfsense/opnsense, but still offers enough features. Personally, I enjoy having full control over all and every detail in my FW, which is only possible with the latter.
Thank you for the hint towards IPv6-PD/resolve topology - my migration to IPv6 is still on the ToDo list!
Responding to cruelty with more cruelty, breeds cruelty.
Registering DHCP leases in the DNS, maybe? There's nothing contradictory between a custom domain and dynamic addresses.
Aesthetics are important! Especially for home use, where you might be looking at your systems all the time.
Aesthetics (or lack thereof when things are messy) does have some direct unconscious cost to mental load, and a direct tension between cleanliness and horror vacui.
https://ignorethecode.net/blog/2014/11/11/horror_vacui/
> And let's not forget, a well-designed system can actually make troubleshooting and maintenance easier. I've seen some beautifully cable-managed rigs that make it a joy to work on. Maybe I've been wrong to dismiss aesthetics all these years... you've got a point, aesthetics maybe matter.
That's where we start talking about "design" instead of "aesthetics"! Dieter Rams's 2 to 6 would definitely apply:
People need to learn, and Internet culture has a real good way to teach.