New version of wsl seems to use wslrelay.exe to take care of network forward
ilazycat opened this issue · 3 comments
ilazycat commented
WSLHostPatcher was running fine until this morning. After some digging around I found that it seems my current version of wsl2 is using wslrelay.exe instead of wslhost.exe to take care of port listening on windows side, which I think cause current version of WSLHostPatcher stop working.
I'm on windows 10 22H2，and my wsl2 version is 1.1.60_x64 (at least base on the binary path). Here's a segment of netstat -anob command output related to wsl. Hope this can help fixing the code.
TCP [::1]:22 [::]:0 LISTENING 17584
[wslrelay.exe]
TCP [::1]:80 [::]:0 LISTENING 17584
[wslrelay.exe]
TCP [::1]:6379 [::]:0 LISTENING 17584
[wslrelay.exe]
ilazycat commented
I've tried to add wslrelay.exe to patch list and it seems working and created a pull request for you to review.
ilazycat commented
Compiled a new version of WSLHostPatcher with wslrelay.exe taken care of.
WSLHostPatcherWithWSLRelay.zip