Live data from Hacker News

Building a Home Lab Beginners Guide

haydenjames.io

101–110 of 184 posts

Re: Building a Home Lab Beginners Guide

#101
post #96

i'm temped to buy the used enterprise equipment but in the end, i ended up buying small Intel NUC machines for my homelab. power consumption of these NUCs is almost negligible while one Dell R620 with dual CPU takes 150-200W at idle.

Same for me. I can fit two Intel NUCs under my monitor stand - one a headless server, another the primary input on the monitor - and can accomplish a decent amount with 16 GB RAM (on an older generation NUC) and two internal drives.

Re: Building a Home Lab Beginners Guide

#104

Mostly skimmed over here, but a key point is that you should be trying to build a cheap version of what you'd use at work. The closer you are to your work environment, the more you can applicably "try things" at home, and bring them to work with you. And since most of us are pretty busy, it's nice to not have to learn a whole new skill set just for maintaining our home networks.

I don't get why we'd pay for and maintain the test environment the employer should have. Should I bring my own printer and laptop to the office too?

I think this misunderstands the point of the parent comment. They're not saying "replicate your work environment so that you can test your things at home", they're saying "replicate your work environment so you can learn best practices and apply your learnings at home when you're at work".

There's a stark difference in that the things you host and do with your home setup are your own, but the learnings and technologies can be applied more broadly.

Re: Building a Home Lab Beginners Guide

#105
post #23

Any recommendations on home networking? I couldn't figure out what the established approach would be to having access to the infrastructure over a consumer internet connection and without exposing the rest of the network. All resources I've seen so far don't give enough background to seem reliable.

I can't replace/reconfigure the router I'm behind right now, so I set up a Wireguard VPN. A $5/mo DigitalOcean droplet is the "hub", which then has point-to-point connections through Wireguard to each of my devices. They all get their own IP addresses through the network—I used the 10.101.101.0/24 subnet for memorability—and since I manually allocate IP addresses, I can actually remember which one is which! Then they can talk to each other through the VPN, and if anything wants to be accessible from the public internet, Nginx on the DO droplet reverse proxies to it. My favorite advantage is that my phone/laptop always have access to my devices at home, even when roaming. Plus, in theory, I could relocate any device to another network with no downtime except the time it takes to physically move it and plug it back in—I haven't tested this yet.

The one downside I've encountered so far is that I often have devices sending traffic from home network -> droplet -> home network, since they "don't know" that they're actually on the same local network, and exclusively communicate through the VPN. My ping to DO's datacenter is low enough that this hasn't really bothered me, though.

Re: Building a Home Lab Beginners Guide

#106
post #94

Router =/= Firewall. If you are planning to host stuff, or even just to protect your own things, you better get something like Sonicwall or similar. At my home I have a sonicwall, synology nas, 2 dell servers, power supplies. Not in a single closet though. To me, the server security is far more important than the looks. Spend the most money on firewall, rest is just for looks. Patch panel for home setup sounds excess…

Maybe a noob question, but why do you need a dedicated firewall appliance? What is it doing for you that just closing all ports and then selectively reopening as needed (my current solution) won't do? What kinds of threats is it protection your network from?

Re: Building a Home Lab Beginners Guide

#107
post #72
post #63

Earlier quoted context omitted.

I have a mini-itx case with 8 5400 rpm drives, and some basic xeon (E12xx, forgetting the exact model), and I'm shocked at how well modern power saving techniques work. When it's just sitting there being a file server it consumes less than 100 watts, and even when I'm pulling from it at over a gigabit it goes up to maybe 110. It also has 120 mm fans, but I barely notice when they kick on. The loudest part of the whol…

Mini-ITX case recommendation that holds 8 3.5" drives please?

I’m very happy with my U-NAS enclosure (NSC-400; 4 hotswap bays), and they do have 8-bay enclosures.

https://www.u-nas.com/xcart/cart.php?target=product&product_...

Re: Building a Home Lab Beginners Guide

#108
One of the reasons I still run some servers and play with networking gear at home, even when SaaSes, Linode, and EC2 are so affordable, is as an exercise in being somewhat more self-sufficient, than depending on "other people's computers" for everything.

Especially since my entire industry seems determined to see how far it can push spying on its users, leveraging power over them, etc. (All evidence is: no real limit yet.)

Also, it's just fun to play with gear.

Currently, I want to engineer for reliability, audible noise, power consumption, and price. (Will a RasPi with its SD card and wallwart be reliable enough? What about an Atom box, with Noctua fans, and mirrored 2.5" drives? Do I really want a pfSense box and some external WiFi APs, or can I make OpenWrt on plastic home routers do everything, and isn't Ubiquiti gear pretty but closed? Remember the price doubles if I want to have cold spares. Has the novelty of the big blue Palo Alto Networks box worn off yet? Can I discreetly mount my rack console in my living room IKEA, without a deep 4-post cabinet, nor the official rails kit?)

Toys get traded on /r/homelabsales, craigslist, and eBay.

Re: Building a Home Lab Beginners Guide

#109

Earlier quoted context omitted.

For a lot of people, a home lab isn't just to provide themselves a service, they actively enjoy the setup and management. So I think your final line is more personal preference than a lesson most people with home labs need to realise.

Yeah, home labbing is about the journey but eventually the journey ends once you've learned how to use some of the technology you wanted.

My home lab helped boost my career enormously. 5 old HP servers running Windows 2000 network introduced me to AD, Exchange, MS-SQL, etc. hooked up via Cisco hardware. (100% pirated I will admit)

The cost of purchasing (eBay) and running the servers paid for itself in 6 months on my first "IT" salary.

I sold on the whole lot to another guy trying to boost his skills too.

It was fun and served its purpose.

Re: Building a Home Lab Beginners Guide

#110
post #78
post #31

I had a fairly large home lab once. I had a fully topped out SPARCserver 1000E and a disk enclosure in my bedroom. I also once lived with an E450 on the kitchen table for a month. But they’re noisy as hell, inconvenient, expensive to keep running and expensive to feed with power and take up a lot of room and thus are not compatible with family and general sanity over time. They become needy balls and chains. So roll…

Your conclusion is wrong, you just found out homelabs is not a hobby for you. People have way more expensive and time consuming hobbies.

Well, I guess if you are serious about a home lab you need both your normal network and a seperate homelab. I like tinkering with my homelab but I need not to depend on it for my work or internet access.
Post reply on HN