u/OmadaNetworks

Building your first homelab is one of those projects where you don’t know what you don’t know.

You start with a router, a switch, and a few clean cables.
Six months later, you’re tracing one mystery Ethernet cable through a spaghetti monster behind the rack.

You buy an 8U rack because “there’s no way I’ll need more than that.”
Then somehow you’re shopping for a bigger one.

You grab some cheap enterprise gear because it looks like a great deal… until you hear the fans.

A lot of people here are building their first homelab right now, and the same questions — and mistakes — tend to come up again and again.

So for this Wednesday’s discussion, we want to collect some of that hard-earned experience in one place. The goal is simple: help someone starting today learn from what you already learned the expensive way — fewer lessons learned through trial and error, less money wasted, and hopefully less rebuilding later.

Homelab veterans: if you were starting your homelab setup from zero today, what would you do differently?

A few things that always seem to come up:

• Rack size & depth: What do first-timers usually underestimate?
• Cable management: What actually keeps a homelab rack from becoming spaghetti?
• Switches, ports & PoE: How much extra capacity should you leave?
• 1G vs. 2.5G vs. 10G: What’s actually worth paying for?
• UPS & power: What should beginners plan from day one?
• Heat & noise: Any enterprise gear you regretted putting at home?
• Buying hardware: What was a complete waste of money?
• Future expansion: What did you outgrow way faster than expected?

And the big one:

What mistake actually forced you to redo part of your homelab later?

Photos are welcome too — especially if you have a first setup vs. current setup comparison.

No need for a full guide. Even a quick “don’t do what I did” could save a first-timer some time and money.

We keep seeing versions of this question from people asking how they should plan a home network when their needs may grow over time.

Some already have a homelab, multiple access points, PoE cameras, a NAS, or home servers. Others may not need any of that today—but they’re wondering what they should prepare for while the walls, attic, or cable routes are still accessible.

And it often comes down to the same question:

What should be wired, and what is perfectly fine on Wi-Fi?

The honest answer is usually “it depends.” But the useful part is understanding what it depends on.

Rather than pretending there’s one setup that works for every home, we thought it would be helpful to collect some real-world experience in one place.

If you were starting over today:

• What would you always wire?
• What would you happily leave on Wi-Fi?
• What did you wire that turned out not to need it?
• What did you leave wireless and later regret?

Maybe that means wiring access points, home offices, gaming PCs, PoE cameras, a NAS or home server—or simply adding drops to places that might become useful later.

The other difficult part is how quickly home networking is changing, especially Wi-Fi and multi-gig networking. Something that feels unnecessary today may become useful later, while something that looks “future-proof” may turn out to be expensive overkill.

If you were planning for the next 5–10 years, what would you prioritize?

Cat6 or Cat6A? Extra drops? Conduit and pull strings? PoE capacity? Fiber to key locations? Space for a rack or additional switches? Preparation for 2.5GbE or 10GbE?

Or would you install only what you need today and avoid spending money on a future setup that may never happen?

For anyone who has already built or gradually grown a more advanced home network:

What aged well, what was overkill, and what is one thing you wish someone had told you before you started?

Hopefully, the experiences shared here can help someone build a network that works for them today, leaves room to grow tomorrow, and avoids opening the same wall twice.

There’s a lot of networking content out there—but finding the genuinely useful stuff isn’t always easy. We’d love to build a community-recommended list of resources that network enthusiasts, IT professionals, installers, and newcomers can actually learn from. Where do you usually go to keep up with networking topics or solve a problem? It could be:

• An industry media outlet, website, newsletter, or blog
• An editor, networking professional, industry writer, or technical expert
• A YouTube channel or content creator
• Any other resource you regularly rely on or think deserves more attention

Recommendations don’t need to be Omada-related—anything genuinely useful is welcome.

Please share the name or link, and, if possible, tell us what you like about it. We’ll collect the most recommended resources and turn them into a community resource list for everyone.

The first Omada Fusion 2.5G units are now making their way into real networks and we know a product page can only answer so much.

We’re opening this thread as a place to ask questions, compare notes, and discuss how Fusion 2.5G works in real network environments. Questions can cover topics such as:

• IDS/IPS performance
• Multi-WAN load balancing and failover
• VLANs, ACLs, and firewall rules
• VPN features and performance
• The built-in Omada Controller
• Migration from an existing Omada setup
• IPv6, DHCP, DNS, and local network management
• Hardware and software design decisions
• Current limitations and areas for improvement

Comparisons with other platforms are welcome when they focus on specific features, workflows, performance, or deployment experience.

Technical, practical, and critical questions are all welcome. The Omada team will follow the discussion and respond where we can. While we may not be able to answer every question immediately, we’ll respond when we have confirmed information to share.

Questions and feedback may also be shared with the relevant product teams for further review.

Already using Fusion 2.5G? Feel free to share your setup, experience, or anything you think other users should know.

Drop your questions below.