Differences
This shows you the differences between the selected revisions of the page.
| 2022-02-05 | 2022-02-05 | ||
| no summary (124.123.68.193) (hidden) (untrusted) | Restored revision 1598011121. Undoing revisions 1644043099, 1644043162. (martin) (hidden) | ||
| Line 32: | Line 32: | ||
| ===== [[tunnel_putty]] Setting up tunnel using PuTTY for SFTP/SCP session ===== | ===== [[tunnel_putty]] Setting up tunnel using PuTTY for SFTP/SCP session ===== | ||
| Note that this is for illustration only, such a simple tunnel can be setup directly in WinSCP. | Note that this is for illustration only, such a simple tunnel can be setup directly in WinSCP. | ||
| + | |||
| + | ==== Setting up the tunnel ==== | ||
| + | In PuTTY configure a session for //Server A//. I.e. particularly fill in //Host Name//. Then switch to //Connection > SSH > Tunnels// page. And add new forwarded port: | ||
| + | * //Source port//: Any free local port, typically above 3000. Example: 3111. | ||
| + | * //Destination//: Hostname and port of the //Server B// separated by colon (the same information you would fill on //Session// dialog of WinSCP if you were connecting directly). The port will typically be SSH port 22. Example: example.com:22. | ||
| + | * Make sure forwarded port type is //Local// (default). | ||
| + | * Click //Add//. | ||
| + | Now start the session. Port forwarding starts to work only once you authenticate to //Server A//. Note that you need to keep the session open as long as you use the tunnel. | ||
| You can also setup a tunnel from command-line: | You can also setup a tunnel from command-line: | ||