On Mon, Jun 2, 2008 at 4:38 PM, Cameron Simpson <cs(a)zip.com.au&gt; wrote: Thanks a lot, I will try it. I followed your hint of ProxyCommand here is the .ssh/config file: Host labpc ProxyCommand ssh lux@gw -t -w 3 labpc 22 When ssh labpc I got two layers of prompt for login. there were possible outputs: 1st, sometime, I got login to labpc , but it last 1 or 2 seconds, and get discconetctd with this message:Connection to labpc closed by remote host. the 2nd output is failure to login and got this message: Write failed: Broken pipe any suggest? thanks Y

On Sat, May 31, 2008 at 1:57 PM, Cameron Simpson <cs(a)zip.com.au&gt; wrote: Sounds a very interesting tool. I gave it a try. But what is shqstr? looks a like a command, but not in my system thanks

On 31May2008 13:57, I wrote: | Conveniently, it can make use of an sshtorc file that maps "name" into an | arbitrary "name1!name2!name3!..." ssh hop path. I routiney get only | certain hosts as "sshto foo" where "foo" designates a multihop ssh path. s/only/onto/ Whoops. -- Cameron Simpson <cs(a)zip.com.au&gt; DoD#743 http://www.cskk.ezoshosting.com/cs/ NFS: Not a File System

Cameron Simpson wrote: It sounds like you have experience with what he is trying to do, so please continue to advice the OP. What he is does now is ssh to PC A, and then ssh to PC B. What he wants to ssh to PC B in one command, but he has to go through PC A. (firewall machine?) Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!

lux wrote: You can try adding the -t option to the command to run on PC A. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le 29.05.2008 14:11, lux a écrit : | Hi, | I routinely login a remote server via a 'gateway' machine. For example, | I need to login to PC B using ssh. But this PC B is behind a | firewall.ssh port on PC A is open. | | As a result, I have to login PC A via ssh, then ssh PC B from PC A. | | Is there ssh command line option that I can directly ssh to PC B? I think that you have to make some firewall rules on your gw to allow NAT to PC B I'm not sure that Mikkel's solution will work: "Pseudo-terminal will not be allocated because stdin is not a terminal" will be the error message. - -- François Patte UFR de mathématiques et informatique Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)1 44 55 35 61 http://www.math-info.univ-paris5.fr/~patte

On 03Jun2008 10:31, lux <yuanlux(a)gmail.com&gt; wrote: | On Mon, Jun 2, 2008 at 4:38 PM, Cameron Simpson <cs(a)zip.com.au&gt; wrote: | > On 02Jun2008 16:23, lux <yuanlux(a)gmail.com&gt; wrote: | > | > >> I have a script called "sshto" that does exactly this for multihop | > ssh | > | > >> connections. [...] | > | Sounds a very interesting tool. I gave it a try. But | > | what is shqstr? | > | looks a like a command, but not in my system | > | > Yeah, sshto shamelessly uses other scripts from that same collection. | > Shqstr quotes strings for handing to eval/sh/remote-ssh intact. | > The simplest thing is to go to: | > http://www.cskk.ezoshosting.com/cs/css/ | > and download the tarball, unpack into /opt/css. [...] | | Thanks a lot, I will try it. Cool. The purpose of sshto is that it knows how to construct the right proxycommand for you:-) Oh yes, you will probably need the "nc" command (netcat) on the gateway machine. Or the target machine, at the expense of an extra hop - I'll elaborate on that if you turn out to need it. This is because, if sshto uses proxycommand (i.e. it is multihop), it uses "nc host 22" to do the final connection to the target ssh daemon (on labpc in your case). | I followed your hint of ProxyCommand | here is the .ssh/config file: | | Host labpc | ProxyCommand ssh lux@gw -t -w 3 labpc 22 | | When | | ssh labpc | | I got two layers of prompt for login. there were possible outputs: | | 1st, sometime, I got login to labpc , but it last 1 or 2 seconds, and get | discconetctd with this message:Connection to labpc closed by remote host. | | the 2nd output is failure to login and got this message: | Write failed: Broken pipe | | any suggest? thanks Yes. Start an ssh-agent, add your key to it, add forwardagent to your ssh config file. Then no prompting will be needed. Pretty much all batch or multihop stuff will need an agent to avoid prompting for passwords. Also, always put ssh options before the "user@host", it is less ambiguous. Eg: ProxyCommand ssh -t -w 3 lux@gw You should not need (and in fact should probably _avoid_) the -t option for the proxy command - it really should not use a terminal. I have not used the -w options myself, and again they should not be in the proxycommand, they should be in your upper-level ssh that _uses_ the proxycommand. I don't know why you have "labpc 22" on the end of that. A guess: Host labpc ProxyCommand ssh lux@gw but be sure to set up ssh-agent first. Cheers, -- Cameron Simpson <cs(a)zip.com.au&gt; DoD#743 http://www.cskk.ezoshosting.com/cs/ Sue Ralph Nader, too, he was supposed to have prevented this kind of thing by now. Oh, and my fee is 40% - Ed "gettabike" Green, rec.motorcycles