[WSL2] Encountered issues on OpenSSH at Ubuntu 20.04 LTS #5244
Comments
|
Just to add another data point, ssh works for:
At least in my particular case. I also attempted to do a distribution upgrade from 18.04 to 20.04 using WSL2, and this also failed to work. |
|
And since @CamberLoid couldn't get a trace, perhaps mine will work as a substitute (our debug output seems similar enough to assume we might be having the same issue): |
for my case it wont work on ubuntu 18.04(WSL 1 & 2) even Ubuntu 20.04(WSL 1& 2). cant do any SSH connection, |
|
I don't believe this actually addresses the problem. If it does, could you explain how? |
|
It's not WSL fault. See your logs: debug1: expecting SSH2_MSG_KEX_ECDH_REPLY Ubuntu SSH to Windows: |
|
The two address have pointed a possible point. |
|
Try this: https://superuser.com/questions/699530/git-pull-does-nothing-git-push-just-hangs-debug1-expecting-ssh2-msg-kex-ecd |
|
Hi there I fix this problem by updating my wifi driver , it seems wsl 2 kinda have problem with old driver based on this link |
I stuck on this problem for weeks, and your suggest is totally work! Thanks! |
|
Please collect WSL logs and post the backlink to the feedback item here. Also please identify any third-party networking software that has been installed on Windows. |
|
Sorry guys, Camber's here. |
|
Thanks for the follow-up Chamber, it is very appreciated. Let's call this spiritually /dupe #4253. Some drivers do not seem to handle mismatched MTUs well. Or, at least that is a plausible working theory. Anyone still seeing the OP fail " |
|
Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! |
ghost
added
the
19624
At local WSL2 Ubuntu 20.04 LTS instance
At remote Ubuntu 20.04 LTS (journalctl -e --unit=ssh.service)
Referring to #4208 , which is closed for a long time:
I encountered the exactly same issue.
It's weird because I don't have the issue on my other WSL2 instance, like debian, and neither does my friend's. As the previous issue is closed for a long time, and even i got my workaround, I think I should open this new issue with some detailed information to figure what's wrong.
I tried, but by runningSee #5244 (comment)strace -o ssh.strace -f ssh -vvv root@hikari.camber.moeit works without any errors, which is so weird.The text was updated successfully, but these errors were encountered: