-----Original Message----- From: John Doe [mailto:jdmls@yahoo.com] Sent: Monday, October 20, 2014 5:30 AM To: CentOS mailing list; Tim Dunphy Subject: Re: [CentOS] rsync question: building list taking forever
Are you "allowed" to temporarily run an ssh tunnel (or stunnel) on your jumpbox? So connecting from host1 to jumpbox on port XXX would be tunneled to ssh port on host2...
Or with netcat (if you can mkfifo)? mkfifo backpipe nc -l 12345 0<backpipe | nc host2 22 1>backpipeBut you will have to trick ssh into accepting your jumpbox "fingerprint"...
JD
Or perhaps easier (depending on how paranoid sshd configs are) with ProxyCommand in ssh/config, i.e., setup config so one ssh command can get you logged onto the final target and then use rsync across ssh as per normal:
http://sshmenu.sourceforge.net/articles/transparent-mulithop.html
Then rsync will be running on both ends, where the data (filesystem information) is LOCAL, i.e., fast.
I would use, if possible/allowed, key[s] with ssh(-agent) to make the whole connect to multiple hosts thing easier (i.e., fewer passphrase requests).
[OP: `they don't allow ssh between the datacenters` ...but... they nfs between them...??? ME: much head scratching.]
Even when this disclaimer is not here: I am not a contracting officer. I do not have authority to make or modify the terms of any contract.