docs(remote-ssh): replace the 127.0.0.1-target advice with the verified VIP pattern - #222
Merged
Merged
Conversation
…ed VIP pattern The Access-for-Infrastructure banner suggested registering the target as 127.0.0.1 to keep sshd loopback-only. That cannot work: the client OS routes loopback to itself, so the traffic never enters WARP. Document the pattern verified live on 2026-08-06 instead — a TEST-NET-1 virtual IP bound to lo, a second ListenAddress, warp-routing on the tunnel, and a /32 private route — plus the unix-username-principal gotcha, the 2026 dashboard locations, and the zero-config phone client path. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The runbook's Access-for-Infrastructure banner recommended registering the SSH target as
127.0.0.1to preserve the loopback-only sshd property. Verified on a live deployment (BusyBee, 2026-08-06) that this cannot work — the client OS routes loopback traffic to itself, so it never enters WARP.This documents the pattern that does work, verified end-to-end from a phone:
192.0.2.1) bound toloonly (persisted via a oneshot unit orderedBefore=ssh.service), secondListenAddress— the invisible-to-the-LAN property survives.warp-routing: enabled: trueon the config-file tunnel +cloudflared tunnel route ip add 192.0.2.1/32.ssh).🤖 Generated with Claude Code