B13 · Tutorial
Our VPN Test Lied: Test a Travel Router Properly (Phase 4.6)
Nothing loads from YouTube until you press play. The video then plays in YouTube’s privacy-enhanced mode. Everything on screen in the Hardware Lab is a training value.
Phase 4, step 4.6 of the Communication Suite build: test the travel router the way the suite's hotel test lab did. Test one isolates the router with a controlled test client and blocks only the router's relay upstream: the client should fail closed, then recover on its own. Test two confirms the path, captures raw packets upstream with tcpdump, and runs nested, low-signature and nested again, reading the PCAP for outer WireGuard, UDP/443, direct TCP and UDP/53. Plus router housekeeping traffic, re-testing after firmware changes, and why IPv6 needs its own test. Test one is shown in the suite's Hardware Lab simulator: the screens are illustrative, and every key, relay and address in them is a training value. The interface name and addresses from the hotel test lab are its examples; use your own.
What you’ll learn
- Isolate and test the router on its own
- Capture and read the real packets
- Know the limits of an IPv4-only test
Chapters
The honest limits
The hotel test lab's interface and addresses are examples. It validated the observed IPv4 path; IPv6 wasn't validated. The results come from the Debian laptop, not the phone. A capture covers only the workloads and transitions captured.