About
In networking, the default gateway is the device your traffic turns to when it doesn't know the route. No entry in the table, no idea where to go next? Send it to the gateway — it'll figure it out from there.
That's exactly what I want this site to be.
The Default Gateway is where I document my journey of learning IT and infrastructure the hands-on way — by building things, breaking them, and documenting the process. Everything published here comes from real projects running on real hardware: a Raspberry Pi 5 home server hosting a growing stack of Docker containers, retired ThinkPads given second lives as lab machines, self-hosted services replacing one cloud subscription at a time, and the scripts that keep it all running.
This site wasn't born in a lecture hall. I entered the IT world without a traditional degree — everything here was learned by experimenting, breaking things, troubleshooting the mess, and earning industry certifications along the way. I'm not a professional educator, and this isn't a classroom. I simply share what I learn, as I learn it — and because I know what it's like to figure things out without a syllabus, every guide is written for the person doing exactly that.
No route in your table yet? That's fine. You've found the gateway.
Homelab & Self-Hosting
Step-by-step walkthroughs for building your own infrastructure: home servers, network-wide ad blocking, private cloud storage, media libraries, VPN routing, and dashboards to tie it all together.
Linux & Automation
The command line, Docker, and the PowerShell and Python scripting that turns repetitive work into a one-liner.
Certification Study Notes
Structured notes and study strategies from working through industry certifications, written to be useful whether you're preparing for an exam or just want the knowledge.
Learning in Public
The honest version of the journey, including the wrong turns. From computer science fundamentals to building this very website from scratch, documented while it's happening.
Every guide here follows one rule: explain the why, not just the what. Anyone can paste a list of commands. I'd rather you understand what each one actually does — 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. Expect troubleshooting sections, honest notes about trade-offs, and configurations you can adapt to your own hardware rather than copy blindly.
Anyone standing where I once stood: curious about servers, networking, Linux, or self-hosting, but not sure which route to take first. You don't need a rack in your basement or a computer science degree — I'm living proof of that. You need curiosity, a spare afternoon, and maybe an old laptop collecting dust in a drawer.
— p@nos