I was taking that same tack... then, I looked again. note: He's on host a, telling
it to ssh to host-b, forwarding port 873 of host-a through the ssh connection to
host-c.
He isn't sshing to the rsync host. He's sshing to a machine that can rsync to host-c.
I thought he was just being stupid, until i realized that. His need is genuine.
He can check to see if the forwarding is working simply by telnetting to port 873. He
should get back something like
++++++++++++++++++++++++++++++++++++
telnet atlas 873
Trying 134.27.18.37...
Connected to atlas.
Escape character is '^]'.
@RSYNCD: 24
++++++++++++++++++++++++++++++++++++
If he doesn't, try forwarding to remote port 23, 21, 25, 80, whatever... i don't know
what ports work on host-c, but he can figure it out in a few seconds, by sshing into
host-b, and trying the appropriate tests.
Heck, we know rsyncd is supposed to be there, so he can ssh to host-b, telnet host-c
873, and see if he gets the above type of message. If so, troubleshoot the
forwarding, if now, find out what port rsyncd IS on.
Tim Conway
[EMAIL PROTECTED]
303.682.4917
Philips Semiconductor - Colorado TC
1880 Industrial Circle
Suite D
Longmont, CO 80501
"There are some who call me.... Tim?"
[EMAIL PROTECTED]@[EMAIL PROTECTED] on 05/31/2001 11:00:37 AM
Sent by: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]@SMTP
cc: [EMAIL PROTECTED]@SMTP
Subject: Re: tunneling rsync through ssh
Classification:
On Thu, May 31, 2001 at 04:17:36PM +0200, thomas graichen wrote:
> "Michael H. Warfield" <[EMAIL PROTECTED]> wrote:
> > On Thu, May 31, 2001 at 01:48:56PM +0200, thomas graichen wrote:
> >> did anyone here get rsync tunneled through ssh working so far?
>
> >> just to make clear what i mean: i only have an ssh connection
> >> to a host b (say mine is host a) and want to rsync stuff from
> >> host c this way (because i can't do it directly due to fire-
> >> wall limitations)
>
> >> host-a> ssh -L873:host-c:873 host-b
> >> host-b>
>
> >> then also on host a
>
> >> host-a> rsync -av localhost::something .
>
> >> always only results in
>
> >> @ERROR: protocol startup error
>
> > Why not use "rsync -av -e ssh {file specifiers} ..."
>
> > Works for me. I use rsync over ssh all the time that way.
> i too - but what if the other end is a public rsync server
> without ssh access for you?
Then how would you establish the ssh tunnel to begin with? Seems
like we have a "rabit stew" situtation (first you catch your rabbit).
If you have the ability to establish an ssh connection to begin with,
you should then have the ability to run rsync from that end using ssh
as the transport. Or am I missing something here?
> t
> --
> thomas graichen <[EMAIL PROTECTED]> ... perfection is reached, not
> when there is no longer anything to add, but when there is no
> longer anything to take away. --- antoine de saint-exupery
Mike
--
Michael H. Warfield | (770) 985-6132 | [EMAIL PROTECTED]
(The Mad Wizard) | (678) 463-0932 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
