Welcome to The Default Gateway

In networking, the default gateway is the device your traffic turns to when it doesn't know the route. No entry in the routing table, no idea where to go next? Send it to the gateway — it'll figure it out from there.

That's the idea behind this site.

Where This Comes From

My path into IT has been largely hands-on. I don't have a traditional computer science degree. What I have is years of working in the industry, pursuing certifications, and spending countless hours building, breaking, and rebuilding things in my homelab.

Over the years I've worked with everything from Raspberry Pis and retired ThinkPads to high-performance workstations with modern GPUs. I've built servers, configured networks, written automation scripts, and occasionally discovered that the problem causing me hours of grief was something embarrassingly simple.

Those experiences have taught me something that no textbook puts quite as directly as it should:

You learn a lot by doing.

What This Site Is

The Default Gateway is my technical notebook — a place to document projects, working configurations, troubleshooting processes, and the reasoning behind every decision.

The emphasis on reasoning is intentional. Anyone can paste a list of commands. What's actually useful is understanding why each command exists — so when something breaks at step 7 (and eventually, something always breaks at step 7), you can reason your way out instead of starting over from scratch.

Every guide here reflects something I've actually built and tested on real hardware. Where there are trade-offs, I'll tell you what they are. Where my approach might not be the only valid one, I'll say so. Technology rarely has a single correct answer, and I'd rather give you a solid foundation to build on than pretend otherwise.

Why a Homelab

It's easy for IT work to become routine. Depending on your role, a day might involve the same categories of problems you've solved hundreds of times before. There's nothing wrong with that — it's part of the job.

But I think it's equally important to maintain the curiosity that brought most of us into technology in the first place.

The homelab is where that curiosity lives. It's where I run experiments that have no ticket number, test configurations that may or may not work, and occasionally build something purely because I want to know whether I can. Not every project needs a practical justification. Some of the most useful things I've learned came from projects that had no obvious purpose at the time.

Who This Is For

If you're an experienced IT professional looking for something new to experiment with — you'll find documented configurations, real hardware setups, and the kind of specific detail that generic tutorials skip over.

If you're earlier in your career and not sure where to start — every guide here is written with the assumption that understanding the concept matters as much as following the steps. You won't just be told what to type.

If you have an old laptop collecting dust and want to find out what you can do with it — welcome. You're in exactly the right place.

Start Somewhere

You don't need expensive hardware or a dedicated server rack to start learning. Use what you have.

An old laptop can become a server. A Raspberry Pi can run a surprisingly capable home infrastructure stack. A virtual machine is a safe place to experiment with anything. Even a problem you don't fully understand yet is an opportunity to learn something that stays with you.

Read. Build. Troubleshoot. Try again. And when something finally works, ask yourself: what happens if I change this?

That's where the next project begins.

---

This site will grow as my work does — new projects, new configurations, new things worth documenting. Some of it will be highly technical. Some will be relatively straightforward. All of it will be honest about the process.

Welcome to The Default Gateway.

Let's get to work.

— p@nos