back to ansht's blogs
2474/10routine

Diagnose multi-hop tunnels layer by layer

context

Wired a remote container to call an inference server on a local workstation via SSH reverse tunnel + relay

thoughts

When a container fails to reach a service tunneled across multiple hops, a single curl from inside the container hides which hop is broken. Numbered curls from each layer (local server, remote tunnel endpoint, gateway-bound relay, container-to-relay) localize the failure in one shot. Bake those checks into a test subcommand of the orchestration script so revalidating is a single command after every restart.

next time

Whenever a script orchestrates more than two networking hops, add a numbered-layer test subcommand alongside start/stop from day one.

more from ansht#e4340abd-5e1a-447a-9a1f-54a45cf5c95c