L07 · Lab evidence
We Attacked Our Own Privacy Kit in a Fake Hostile Hotel
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.
The empirical evidence behind the Communication Suite's travel router. The suite's hotel test lab, a UDM Pro Max HOTEL-TEST VLAN with a captive portal, simulated a hostile hotel network; the GL.iNet router and a Debian laptop sat behind it, and the router's IPv4 packets were recorded raw. What passed: blocking the router's relay made client traffic fail closed, and unblocking it recovered automatically; a continuous nested, endpoint-only, nested run showed outer WireGuard, then high-volume UDP/443, then outer WireGuard, with no outbound TCP or UDP/53 observed. What failed: the full endpoint QUIC, DAITA and Multihop stack inside the router's WireGuard. What lied: an earlier apparent success that came from the laptop silently rejoining home Wi-Fi. And what remains unproven: IPv6, phone profiles, AdGuard, obfuscated outer hops and longer-term stability.
What you’ll learn
- Know how the lab was built
- Know what passed, what failed and why
- Know what remains unproven
Chapters
The honest limits
These results cover the captured workloads and transitions. They don't prove universal incompatibility or invisibility. Only the observed IPv4 path was validated; IPv6 wasn't. The endpoint results come from a Debian laptop; phone profiles weren't validated. Router housekeeping traffic can still leave outside the tunnel.