Dave Howorth wrote:
mb1-knetdome wrote:
Is there some way to set up a connection from my home machine through the gateway to my work machine that makes the gateway become invisible? So I can run programs that open connections from my home machine to my work machine or vice-versa?
A couple of options:
0. SSH to the gateway as usual, setting up a forwarded port to the SSH port of your internal machine. You shouldn't need to enable X forwarding on this first connection since it doesn't sound like you're actually running anything X from the gateway. Then start another SSH session, using X forwarding, on your home machine but connect to the localhost port that you forwarded to your internal machine. This should work but might be a little slow due to the SSH-inside-of-SSH encryption going on but it sounds like you were kind of doing that anyway.
This sounds interesting, and it appears to work in my testing at work. I'll try it for real tonight. I didn't understand the description at first sight, so for anybody else who didn't either, here's an example of the command lines. Suppose the machines are called 'home', 'gateway' and 'work' and I want to start xeyes on 'work' and see the result on 'home':
In one terminal: home$ ssh -L 2222:work:22 gateway SOME PASSWORD STUFF HERE gateway$
Then in another terminal: home$ ssh -X -p 2222 localhost MORE PASSWORD STUFF work$ xeyes
and the eyes come up on my 'home' machine.
I tried this from home and it didn't work :( Good to know Murphy's alive and well. My problem was passwords. When I do the second ssh, it asks me for the password for 'dave@localhost'. I tried my password on that home machine, my password on the gateway machine (different username, btw), my password on my work machine and no password at all. None worked. Anybody have any idea what I'm doing wrong? Thanks, Dave