Page History

...

Host ioc-* cpu-*
User                  laci
SendEnv               TERM=xterm
HostName              %h.slac.stanford.edu
ProxyCommandProxyJump          ssh -X gateway /usr/bin/nc %h %p <gateway>
StrictHostKeyChecking no
UserKnownHostsFile    /dev/null

...

Host gateway
User           myself
ProxyCommand   ssh -X firewall /usr/bin/nc %h %p

However, as Faisal has pointed out - in the most common use-case the `ProxyJump` directive is more convenient:

Host gateway
User           myself
ProxyJump      firewall

Now when you say

bash$ ssh cpu-b12-xyz

herethen ssh will transparently set up the multi-hop connection. Note that others options can be passed and work as expected, i.e., you can set up port forwarding to the target machine, e.g.,

...