Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • This does not seem to work, even though I have shared keys and can ssh from PC1 or PC2 to jumpbox without password, AND from jumpbox to PC1 and PC2 without password, adding -vvv to the ssh portion of rsync shows that after it connects to jumbox, then attemps to connect to pc2-via-jumpbox at 127.0.0.1:39998, it ikeeps asking for a password and fails. Commented May 25 at 22:05
  • @number9 Obviously you need the private key for PC2 on PC1 (you can define the one to be used in the config file, too). However, this is neither an rsync nor an SSH port forwarding problem at this point any more. You may set LogLevel DEBUG (and reload the service) in /etc/ssh/sshd_config to better understand the problem. Commented May 25 at 22:12
  • Interesting, I placed the key on PC1, no go. It enters some kind of loop that is hard to debug, even with debug. It asks for a password regardless of key placement, and seems to fail with disconnect from UNKNOWN port 65535, too many auth failures (interesting again, 65535, that is the maximum port number). Commented May 25 at 23:57
  • In the debug, it seems that after the initial connection to jumpbox, it tries to then connect back to jumpbox, which then fails (I figured this out as it keeps asking for a password no mater which I use, and then jumpbox password works, which is different). Commented May 26 at 0:03