reports about "SSH Jumphost using cygwin ssh"

[av930]

I was trying to find use Jumphost from "VSCode(Windows) > JumpHost(Linux)> Destination (Linux)"

In result, I successfully connected to server and could debug some python code. however I found a unstable connection between them, sometimes connection re-established. it was trivial.

1. ~/.ssh/config

    Host MyHost
    HostName 10.~~~
    User joongk.kim
    Port 22
    StrictHostKeyChecking no
    UserKnownHostsFile=~/.ssh/known_hosts
    
    Host MyHonda
    HostName 10.~~~
    User integrator
    Port 22
    ProxyJump MyHost

2. VSCode Setting

I think this would be helpful to others.

p.s : ssh is not openssh, it is native binary.

[av930]

I found some warning message in sever.

Warning!! Authorized users only. All activity may be monitored and reported.
319078673c63: running
Acquiring lock on /home/integrator/.vscode-server/bin/da76f93349a72022ca4670aaa2/vscode-remote-lock.integrator.da
Found existing installation at /home/integrator/.vscode-server/bin/da76f93349a72022ca4670c1b8a2...
Checking /home/integrator/.vscode-server/.da76f93349a72022ca4670c1b8486aaa2.log and /home/integrator/.vscode-server/. a running server
Looking for server with pid: 20382
Found running server...

*
* Reminder: You may only use this software with Visual Studio family products,
* as described in the license (https://go.microsoft.com/fwlink/?linkid=2077057)
*

Checking server status on port 34799 with wget
319078673c63: start
SSH_AUTH_SOCK====
DISPLAY====
webUiAccessToken====
listeningOn==34799==
osReleaseId==ubuntu==
arch==x86_64==
tmpDir==/run/user/8100==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
extInstallTime====
serverStartTime====
connectionToken==8402dccd-c820-472a-8dde-7ac87390c292==
319078673c63: end

[gregvanl]

Moving to the vscode-remote-release repo to investigate the connection stability and also think about the best way and place to highlight the workaround

[vscodenpa]

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!