Timeline for Start port forwarding between two remote machines from a third computer
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 17, 2023 at 22:09 | answer | added | Kamil Maciorowski | timeline score: 0 | |
| Oct 17, 2023 at 21:23 | answer | added | DavidT | timeline score: 0 | |
| Oct 17, 2023 at 19:51 | history | edited | Kamil Maciorowski | CC BY-SA 4.0 |
let's keep the question technical
|
| Oct 17, 2023 at 19:48 | history | edited | manifold_destiny | CC BY-SA 4.0 |
added 209 characters in body
|
| Oct 17, 2023 at 19:47 | answer | added | Santafe | timeline score: 0 | |
| Oct 17, 2023 at 18:40 | comment | added | manifold_destiny | The machines I am using run an older version of ssh which does not support ProxyJump. In any case, wont the jump command run a tunnel from remote_2 to compute_mine via remote_1 ? I would need a tunnel between only remote_1 and remote_2. Computer compute_mine should not listen, only issue the command for the tunnel between remote_1 and remote_2 to start. | |
| Oct 17, 2023 at 17:52 | comment | added | Cpt.Whale |
Do you get the same thing if you try -J instead, like ssh -J remote_1 user@remote_2 from compute_mine? The banner exchange error you got looks like ssh choked on the banner from the server side - take a look through the troubleshooting steps here unix.stackexchange.com/q/656631/247007 to see if you can suppress it or get a more detailed error
|
|
| S Oct 17, 2023 at 17:05 | review | First questions | |||
| Oct 17, 2023 at 18:09 | |||||
| S Oct 17, 2023 at 17:05 | history | asked | manifold_destiny | CC BY-SA 4.0 |