This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
ssh_tunneling [09/01/2021 09:28] – gisele_h | ssh_tunneling [10/05/2022 16:23] – gisele_h | ||
---|---|---|---|
Line 3: | Line 3: | ||
{{: | {{: | ||
- | **Recommended software for Tunneling**: updated Sept 1, 2021 | + | ** SSH tunneling using Putty :** |
- | SSH Tunnel Client, free of use, easier then Putty SSH tunneling | + | From @steph06: |
+ | |||
+ | In case you want to set-up several nodes for minting redundancy, find here below an overview of the configuration that could be implemented thanks to SSH tunneling. | ||
+ | |||
+ | It is assumed here that you have one PC in which you have a UI installed and that will be able to communicate alternatively to each one of your core. | ||
+ | |||
+ | If you just have one core to be controlled in remote, you can use the same principle to communicate with, just by keeping the same Source & Destination Port 12391. | ||
+ | |||
+ | Note: Click on the images below for a larger view of the steps and processes. | ||
+ | |||
+ | {{:: | ||
+ | |||
+ | {{:: | ||
+ | |||
+ | |||
+ | **SSH Tunnel Client software for Windows computers **: updated Sept 1, 2021 | ||
+ | |||
+ | SSH Tunnel Client, free of use, easier then Putty SSH tunneling. not recommended for Torchie images use putty. | ||
It can be minimized unlike Putty. Plus, you can add infinite tunnels this way. | It can be minimized unlike Putty. Plus, you can add infinite tunnels this way. | ||
Line 21: | Line 38: | ||
{{: | {{: | ||
- | then connect it. It will show a lock sign. Means tunnel connected. | + | Then connect it. It will show a lock sign. Means tunnel connected. |
{{: | {{: | ||
- | open the UI and add your 127.0.0.1: | + | Open the UI and add your 127.0.0.1: |
End of SSH Tunnel Client set up. | End of SSH Tunnel Client set up. | ||
- | |||
- | |||
- | |||
- | **Other info using SSH tunneling capabilities** : | ||
- | |||
- | From @steph06: | ||
- | |||
- | In case you want to set-up several nodes for minting redundancy, find here below an overview of the configuration that could be implemented thanks to SSH tunnelling. | ||
- | |||
- | It is assumed here that you have one PC in which you have a UI installed and that will be able to communicate alternatively to each one of your core. | ||
- | |||
- | If you just have one core to be controlled in remote, you can use the same principle to communicate with, just by keeping the same Source & Destination Port 12391. | ||
- | |||
- | Note: Click on the images below for a larger view of the steps and processes. | ||
- | |||
- | {{:: | ||
- | |||
- | {{:: |