Timeline for How to rsync files between two remotes?
Current License: CC BY-SA 4.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 22, 2024 at 11:00 | comment | added | Chris Davies | For closure, ↑ this comment ↑ was answered here | |
| Mar 4, 2024 at 8:57 | review | Suggested edits | |||
| Mar 4, 2024 at 13:34 | |||||
| Aug 23, 2022 at 7:59 | history | edited | Chris Davies | CC BY-SA 4.0 | clarify which path is where |
| Nov 25, 2021 at 21:29 | comment | added | sancho.s ReinstateMonicaCellio | I tried this here. I received Connection closed by host1 port 22. I cannot make sense the message in the light of your comment "a reverse channel from port 50000 on host1... to port 22 on host2". | |
| Jul 14, 2021 at 18:03 | review | Suggested edits | |||
| Jul 14, 2021 at 18:41 | |||||
| Sep 17, 2020 at 22:48 | comment | added | Jean-Bernard Jansen | @FlorenzKley you can mix Kevin Cox's technic with this one | |
| Aug 21, 2017 at 8:28 | comment | added | Chris Davies | @CedricKnight agreed. My answer address the question as I interpreted it, and in many cases it should be sufficient. In more complex situations one needs a more complex solution. | |
| Aug 21, 2017 at 8:15 | comment | added | Cedric Knight | 'Assuming the two servers can't talk directly to each other'. This solution does work around a firewall or NAT issue that prevents a direct SSH connection. However, it doesn't address the case where for security reasons the source user (on host1) has no key or credentials or insufficient write permissions on the destination. For that see Kevin Cox's solution, or resort to an indirect connection using a script or scp -3. | |
| May 3, 2016 at 9:15 | comment | added | Chris Davies | @FlorenzKley oh I see what you mean. I'd already mentally swapped "remote" and "local" so that the words were used in the context of the reverse connect. Yes, you're right: in the context of the original connection, the reverse tunnel can only use the "remote" host's ~/.ssh/config file. | |
| May 3, 2016 at 7:59 | comment | added | Florenz Kley | @roaima that was more a "mental note to self". It reads it's config, on the remote server, so alias configuration is to be interpreted in the scope of the executing host, it's the remote's shell that is running here after all | |
| Apr 29, 2016 at 11:22 | comment | added | Chris Davies | @Florenz the reverse connect does read the ~/.ssh/config but as the remote host is mapped as localhost on port 50000 it's probably not matching your configuration | |
| Apr 29, 2016 at 10:40 | comment | added | Florenz Kley | the reverse connect does not read the ~/.ssh/config on the local side - need to use something that can be resolved as if there were no SSH config file | |
| Mar 9, 2016 at 18:01 | vote | accept | kenorb | ||
| Feb 7, 2015 at 18:22 | history | answered | Chris Davies | CC BY-SA 3.0 |