Would you voluntarily spend another five hours on this kind of problem? Why?
Network Engineering · 60–90 min
Trace one request through your own lab
Experience packet evidence and controlled failure diagnosis rather than command collecting.
Start the experiment01 · Setup
What you need
- Basic IP/DNS knowledge, Wireshark installed and permission to capture your own loopback traffic. Installation time is separate. Do not capture shared Wi-Fi or other people’s traffic.
You may stop when the timebox ends. An incomplete result is still useful evidence.
02 · Task
The work sequence
- 01
Start a tiny HTTP server on loopback with a tool you already know. Record its address and port; sketch browser → loopback → server.
- 02
Select only the loopback interface and filter for your server port. Request a harmless local page; stop capture immediately afterwards.
- 03
Find the TCP conversation and HTTP response. Explain source/destination ports and why this local request needs no router hop.
- 04
Stop only your test server, repeat the request and compare failure evidence. Restore it and verify recovery; do not change system-wide firewall or DNS settings.
- 05
Write a short incident note: symptom, evidence, cause, fix and what the lab cannot prove. Keep packet captures private and remove any sensitive payload before sharing.
03 · Pay attention
Watch your reaction, not only the output
- Did tracing the failure feel more satisfying than guessing a fix?
- Can a peer distinguish your observation from your explanation?
Plot twist
Difficulty does not mean the career is a bad fit. The useful question is whether curiosity returned after the difficulty.
04 · Reflect
Three honest questions
Which part gave you energy, and which part drained it?
What evidence—not a salary video—would you gather before choosing this path?
This site does not save your answers. Put them in your own notebook if useful.
05 · Where to go next