💾 Archived View for warpengineer.space › entries › ssh-proxycommand-for-jumping-server.gmi captured on 2024-08-31 at 11:38:50. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-01-29)
-=-=-=-=-=-=-
+--+
| |
| | +--------------------------+
+--------------------------+ | | | |
| | | | | |
| | +-----+--+-----+ | |
| | | | | Remote Machine (C) |
| Local Machine (A) | | | | |
| | | | | |
| | | Jump Server | | |
| | | | | |
| | | (B) | | |
| | | | | |
| | | | | |
| | | | | |
| | | | +--------------------------+
+--------------------------+ | |
+-----+--+-----+
| |
| |
| |
+--+
Machine A can get to Machine B
Machine B can get to Machine C
Machine A **CAN NOT** get to Machine C directly.
Most people will use SSH to connect from Machine A to Machine B, then use SSH again to connect from Machine B to Machine C.
Add the following to SSH config
Host hostb
User myself
Hostname machineB
Host hostc
User myself
Hostname machineC
Port 22
ProxyCommand ssh -q -W %h:%p hostb
With this configuration, SSH can be used to connect directly from Machine A to Machine C. SSH will automatically direct the connection through Machine B.