WSL mirrored networking + VS Code WSL extension

[bamurtaugh]

As discussed on GitHub and offline, creating an issue to track VS Code user feedback that users are experiencing issues with WSL mirrored networking.

Here's the issue: microsoft/vscode-remote-release#9222. Here is an example of traces/logs: microsoft/vscode-remote-release#9222 (comment).

cc @craigloewen-msft

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• Networking mirrored can't work on WSL2 (#10632), similarity score: 0.73
• Cannot enable Mirrored network on WSL (#11154), similarity score: 0.72

Closed similar issues:

• Questions: implementation of WSL 2 networking (#4346), similarity score: 0.70

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[diagonjope]

WslLogs-2024-07-16_13-02-22.zip

@aeschli the wsl netwroking log file is 126 MB. Github has a max allowance of 25 MB. Where should I drop the log

[aeschli]

@keith-horton Do you want the wsl networking file?

More context can be found here:
https://stackoverflow.com/questions/78733419/can-not-connect-vscode-to-wsl2-running-ubuntu-22-04
microsoft/vscode#221727

[keith-horton]

Can you please share your VSCode configuration / docker configuration / docker-desktop configuration?

We have tested with a few VSCode configurations and haven't repro'd issues.

If the log is too large, can you share through onedrive / google drive?

It's not clear why the trace would be that huge though :)

I would recommend:

• start the trace
• wsl --shutdown
• launch VS
• repro the problem
• stop the trace

[diagonjope]

Greetings @keith-horton !

Here you go:

WslNetworkingLogs-networkingMode_mirrored_disabled_2024-07-18_16-00-23.zip

WslNetworkingLogs-networkingMode_mirrored_enabled_2024-07-18_15-58-08.zip

Docker_settings.json

VSCode_settings.json

Let me know if you need anything else from me.

Cheers,

++José

[CatalinFetoiu]

thanks for sending the logs

unfortunately the tcpdump packet capture was not collected (the tcpdump.log file in the zip is empty)

could you please check if you have tcpdump installed in your linux distribution. if not, can you please install tcpdump and collect the logs again?

in the stackoverflow link, you shared VSCode terminal output and renderer.log file in the VSCode logs - can you please share those again for the latest repro? they showed some network connections timing out, that information will be helpful to narrow down the logs

thanks

[diagonjope]

Hi @CatalinFetoiu ,

Here you go:

• 20240719T162955_networkingMode_mirrored_enabled.zip

• 20240719T164240_networkingMode_mirrored_disabled.zip

• WslNetworkingLogs-networkingMode_mirrored_disabled_2024-07-19_16-33-32.zip

• WslNetworkingLogs-networkingMode_mirrored_enabled_2024-07-19_16-29-26.zip

It seems there are several traces showing incorrect udp checksum in the tcpdump.log NetworkingMode_mirrored_enabled zip.

Cheers,
++José

[netux]

Just chipping in for people looking as to why VSCode fails to connect when WSL is configured with networkingMode=mirrored.
I was looking at the docs in Microsoft's website[^1] and noticed there is a note about running some commands to allow the firewall to accept inbound connections from WSL:

Run the following command in PowerShell window with admin privileges to Configure Hyper-V firewall settings to allow inbound connections: Set-NetFirewallHyperVVMSetting -Name '{40E0AC32-46A5-438A-A0B2-2B479E8F2E90}' -DefaultInboundAction Allow or New-NetFirewallHyperVRule -Name "MyWebServer" -DisplayName "My Web Server" -Direction Inbound -VMCreatorId '{40E0AC32-46A5-438A-A0B2-2B479E8F2E90}' -Protocol TCP -LocalPorts 80.

The documentation doesn't go into detail as to what exactly Set-NetFirewallHyperVVMSetting/New-NetFirewallHyperVRule do, but my guess is the first command disables the firewall for any connections coming from WSL, while the second one does the same but only for TCP connections on port 80.

I ran the first command and, after restarting the WSL distro, VSCode was able to connect to it again 🙂

[1]: https://learn.microsoft.com/en-us/windows/wsl/networking#mirrored-mode-networking

[keith-horton]

Hi there.

Yep, your understanding is very close.

Set-NetFirewallHyperVVMSetting -Name '{40E0AC32-46A5-438A-A0B2-2B479E8F2E90}' -DefaultInboundAction Allow

This sets the default to Allow any inbound connection -- but if there are Block rules for inbound connections, those will still apply.