A network engineer writing down what the work teaches

I work with networks and networking every day, and this blog is where I write about the protocols, hardware and connection details I run into.

Working on production networks taught me that most problems come down to a few details: how a route is advertised, how a switch learns an address, or how a link negotiates its speed. Those details are easy to miss when you are busy, and they are hard to explain clearly to someone new to the field. That gap is why I started writing. Each article is my attempt to work through a topic step by step, check it against real packet captures, and explain it in plain language.

I am not writing to sell anything or to follow vendor trends. The goal is simple: document what I see in the field, share what I have learned, and make the fundamentals of networking easier to understand for colleagues and students alike.

I check claims about protocol behavior against actual captures before I publish them, so the explanation matches what the wire really shows.

A network diagram should show only what the reader needs to follow the idea. I remove extra links and labels until the connection is easy to trace.

I aim for short sentences and concrete examples. If a term needs defining, I define it once and then use it consistently.