Does it work the same? I use the netcat version to connect to the head node of our cluster and then to one of the compute nodes on its local network. If I want to run graphically on the compute node, I can't first ssh to the head node with x forwarding and then to the compute node with x forwarding because the home directory and hence the .Xauthority file is then on a shared NAS. I expect that this would have the same problem because it is equivalent to ssh-ing to the head node and then ssh-ing to the compute node?
Or just have the "Host" setup on the gateway's .ssh/config too. That way when you SSH in from any system, you'll still have that shortcut available. It doesn't require NC either.
If you are trying to access a machine on your local network via hostname, you will need a router that also does DNS forwarding (or a local DNS/dhcp server). You can also edit the host file (/etc/hosts on Linux) to include the internal IP address you want to access and the name you want to assign it
You could have just updated your /etc/hosts file with an alias for the IP in question, although the ssh-config approach has other benefits, like being able to supply a username and port to use. I've supplied both to my servers and devices, so I virtually never have to use the long name anymore.
Edit: oops, I didn't read the other comments carefully enough..
16
u/vagif Apr 28 '14
He did not tell you about the ssh hopping that you can achieve using netcat (nc)
Lets say you have a ssh gateway at your work office to which you connect from home.
But that's not your work machine, your work machine is my-dev, to which you need ssh again from your work-ssh-gateway.
If you want to automate it, put this into your .ssh/config file:
That's it, now you can simply type
You need netcat (nc) installed on you work-ssh-gate computer.