PROBLEM
Tools exist, the map does not: nobody knows what listens or which zone may talk to which.
PODEJŚCIE
A small drawn lab network and repeatable inventory and capture exercises.
ARCHITECTURE
- a few hosts in lab zones
- one traffic observation point
IMPLEMENTATION
- addressing and names
- port inventory in the lab
- DNS / TCP exercise with notes
RESULT
- network troubleshooting cheat sheet as a resource
- zone sketches in lab notes
- no client audit report
LESSONS
- without a map every network alert is guessing
Goal
The network lab teaches visibility: what listens, what talks, what a packet looks like. It is not a pentest offer against someone else’s infrastructure.
Two problems I solved
1. Tools without a map
I could run Nmap and Wireshark, but I had no zone drawing. A “weird traffic” alert had no context: from where, to where, should it exist at all.
What I gained: the habit of addressing + host names + who may talk to whom first, then scanning my own lab. The troubleshooting cheat sheet keeps the question order.
2. Exposure “because it ended up that way”
Services landed on defaults; ports stayed open “for a moment”. There was no exposure list to close.
What I gained: listener inventory drills and an internet exposure worksheet. I know which ports are intentional and which are debt.
What I practise
- a small lab topology (practice LAN / DMZ),
nmaponly against my own addresses,- DNS and TCP with notes (expected vs observed),
- one capture point (Wireshark / tcpdump).
Related deployment project: OpenVPN on Oracle Cloud — a tunnel instead of exposing services directly.
Related material
Boundaries
Scan only the own lab. No attacks on third-party Wi‑Fi, no production red team, no “invisible network” promise.
Status
development. Exercises and the cheat sheet are public; a “production” topology does not exist, because this is not production.