-
Notifications
You must be signed in to change notification settings - Fork 837
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WSL2 SSH client hangs during expecting SSH2_MSG_KEX_ECDH_REPLY
#9110
Comments
Usually a MTU problem |
Yeah, a lot of people say that twiddling their MTU on the WSL NICs addresses this. Without being a networking expert, that seems ridiculous to me, and is strongly indicative of something weird in the host->vm networking stack. |
I just encountered the same issue. I set MTU to 1350 like #4253, and it works. |
This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request. Thank you! |
For me it helped only the reducing list of supported MACs:
You can add it to the .ssh/config:
|
Version
Microsoft Windows [Version 10.0.22621.755]
WSL Version
Kernel Version
Linux version 5.15.68.1-microsoft-standard-WSL2 (oe-user@oe-host) (x86_64-msft-linux-gcc (GCC) 9.3.0, GNU ld (GNU Binutils) 2.34.0.20200220) #1 SMP Mon Sep 19 19:14:52 UTC 2022
Distro Version
Debian
Other Software
Connecting to
OpenSSH_8.9p1 Ubuntu-3, OpenSSL 3.0.2 15 Mar 2022
Repro Steps
Repro (for me) consists of
ssh me@my-remote-machine
. It is 100% reproducible when SSHing from WSL; it is 100% non-reproducible when SSHing from Powershell.This started happening after I installed the following updates on Windows:
Expected Behavior
ssh client sets up the connection/session
Actual Behavior
ssh client hangs
Diagnostic Logs
SSH server has this log statement spammed every time I attempt to connect from WSL:
ssh -vvv me@my-remote-machine
shows this from WSL:which suggests that the final packets in the key exchange are getting lost.
The text was updated successfully, but these errors were encountered: