On Thu, 2005-12-08 at 16:37 -0800, Ed Morrison wrote:

I am trying to use rsinc to tranfer my ftp directory from one server to another. I have port 22 closed off due to port knocking and I am trying to direct rsync to use another port. Unfortunately I can't seem to get it to use the specified port. Here is my command, if someone could point out my error I would appreciate it:

rsync -avr --port=XXX xxx.xxx.xxx.xxx:/var/ftp /var/ftp

-e "ssh -p XXX"

You want to pass the port parameter to ssh not to rsync use:

rsync -e "ssh ssh-parameters-here" ... so rsync -e "ssh -p port#" ...

On Thu, 8 Dec 2005, Ed Morrison wrote:

I am trying to use rsinc to tranfer my ftp directory from one server to another. I have port 22 closed off due to port knocking and I am trying to direct rsync to use another port. Unfortunately I can't seem to get it to use the specified port. Here is my command, if someone could point out my error I would appreciate it:

rsync -avr --port=XXX xxx.xxx.xxx.xxx:/var/ftp /var/ftp

The error this generates is:

ssh: connect to host xxx.xxx.xxx.xxx port 22: Connection refused rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(359)

Thanks,

Ed _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

On 12/8/05, Ed Morrison edward.morrison@gmail.com wrote:

I am trying to use rsinc to tranfer my ftp directory from one server to another. I have port 22 closed off due to port knocking

Just thought I'd note--"port knocking" is actually a security scheme you'd use to prevent "port scanning," which is what you're really trying to avoid by changing ssh ports.

I know you might have just typed it without realizing it, but I wanted to mention it just in case. "Port Knocking" is actually a pretty cool thing (that isn't widely implemented yet, as far as I know).