This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
ssh_tunneling [03/20/2021 00:14] – created gfactor | ssh_tunneling [10/05/2022 18:18] (current) – gisele_h | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== SSH Tunneling ====== | ====== SSH Tunneling ====== | ||
- | @steph06: | + | {{: |
- | in case you want to set-up several nodes for minting redundancy | + | |
+ | ** SSH tunneling using Putty :** | ||
+ | |||
+ | 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. | 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. | 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. | ||
- | Don't hesitate to comment or correct for better clarifications. | + | |
- | Thanks to < | + | Note: Click on the images below for a larger view of the steps and processes. |
{{:: | {{:: | ||
{{:: | {{:: | ||
+ | |||
+ | |||
+ |