search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.37k stars 817 forks source link

Starting VPN failed when WSL with networkingMode=mirrored is running #10830

Open kgh02017 opened 10 months ago

kgh02017 commented 10 months ago

Windows Version

Microsoft Windows [Version 10.0.22621.2715]

WSL Version

2.0.11.0

Are you using WSL 1 or WSL 2?

Kernel Version

5.15.133.1-microsoft-standard-WSL2

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

  1. Run WSL with networkingMode=mirrored
  2. Try to run VPN

Expected Behavior

Starting VPN succeed with no error

Actual Behavior

Starting VPN failed and got RasClient error 651 in EventViewer

image

image

Diagnostic Logs

No response

github-actions[bot] commented 10 months ago

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:

Closed similar issues:

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

ghost commented 10 months ago

/logs

kgh02017 commented 10 months ago

This is the logs. WslLogs-2023-11-29_13-44-01.zip

CatalinFetoiu commented 10 months ago

@kgh02017 can you please collect logs for networking issues, using the instructions at link below? thanks https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues

kgh02017 commented 10 months ago

@kgh02017 can you please collect logs for networking issues, using the instructions at link below? thanks https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues

sure

WslNetworkingLogs-2023-12-07_11-23-29.zip

CatalinFetoiu commented 1 month ago

thanks for adding the logs. sorry for the delay following up on this

we'll also need some VPN traces to be able to troubleshoot

could you please do the following steps to collect new logs?

1) in admin cmd window, run: netsh trace start scenario=VpnClient provider={90BBBABB-255B-4FE3-A06F-685A15E93A4C} keywords=0xFFFFFFFFFFFF level=0xFF provider={E6DEC100-4E0F-4927-92BE-E69D7C15C821} keywords=0xFFFFFFFF level=0xFF provider={2588030C-920E-4AD5-ACBF-8AA2CD761DDB} keywords=0xFFFFFFFF level=0xFF per=yes report=dis maxsize=0 filemode=single corr=dis tracefile=nettrace.etl

2) in admin powershell window, run: .\collect-networking-logs.ps1

3) reproduce the issue

4) stop collect-networking-logs.ps1

5) in the admin cmd window, run: netsh trace stop

6) collect and share nettrace.etl and the WslNetworkingLogs zip

kgh02017 commented 1 month ago

in admin cmd window, run: netsh trace start scenario=VpnClient provider={90BBBABB-255B-4FE3-A06F-685A15E93A4C} keywords=0xFFFFFFFFFFFF level=0xFF provider={E6DEC100-4E0F-4927-92BE-E69D7C15C821} keywords=0xFFFFFFFF level=0xFF provider={2588030C-920E-4AD5-ACBF-8AA2CD761DDB} keywords=0xFFFFFFFF level=0xFF per=yes report=dis maxsize=0 filemode=single corr=dis tracefile=nettrace.etl

When running the above commad, I got the following error message:

netsh.exe: The command parameter was already specified.

CatalinFetoiu commented 1 month ago

@kgh02017 thanks for following up that's odd - are you running this in an admin cmd or in powershell?

kgh02017 commented 1 month ago

Powershell(admin)

image

CatalinFetoiu commented 1 month ago

@kgh02017 thanks. can you try the same command in an admin command prompt windows (not in powershell)? netsh has some subtle issues when ran in powershell

kgh02017 commented 1 month ago

I could finally get log and trace.

nettrace.zip WslNetworkingLogs-2024-09-04_08-27-52.zip

github-actions[bot] commented 1 month ago

Failed to parse logs. Unexpected file: nettrace.etl The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information ``` Multiple log files found, using: https://github.com/user-attachments/files/16858746/nettrace.zip Found no WSL traces in the logs ```
CatalinFetoiu commented 1 month ago

@kgh02017 thanks for sending the traces. Sorry, we need to collect some additional files to narrow down the error can you please do the following in an admin command prompt?

netsh ras set tr * en

netsh trace start scenario=VpnClient provider={90BBBABB-255B-4FE3-A06F-685A15E93A4C} keywords=0xFFFFFFFFFFFF level=0xFF provider={E6DEC100-4E0F-4927-92BE-E69D7C15C821} keywords=0xFFFFFFFF level=0xFF provider={2588030C-920E-4AD5-ACBF-8AA2CD761DDB} keywords=0xFFFFFFFF level=0xFF per=yes report=dis maxsize=0 filemode=single corr=dis tracefile=nettrace.etl

netsh trace stop netsh ras set tr * di Collect and share all the files under C:\windows\tracing Collect and share nettrace.etl
kgh02017 commented 1 month ago

WslNetworkingLogs-2024-09-05_08-23-27.zip nettrace-20240905.zip

github-actions[bot] commented 1 month ago
Diagnostic information ``` Multiple log files found, using: https://github.com/user-attachments/files/16881996/WslNetworkingLogs-2024-09-05_08-23-27.zip .wslconfig found Detected appx version: 2.0.11.0 optional-components.txt not found ```
CatalinFetoiu commented 1 month ago

@kgh02017 thanks - can you please also share the files in C:\Windows\tracing? please make sure you also ran the "netsh ras set tr en" and "netsh ras set tr di" commands from my previous reply

kgh02017 commented 1 month ago

please make sure you also ran the "netsh ras set tr en" and "netsh ras set tr di" commands from my previous repl I did. tracing.zip

github-actions[bot] commented 1 month ago

No logs.etl found in the archive. Make sure that you ran collect-wsl-logs.ps1 as administrator and that the logs.etl file is in the archive.

Diagnostic information ``` appxpackage.txt not found optional-components.txt not found No logs.etl found in archive. Error while parsing the logs. See action page for details ```
kgh02017 commented 1 month ago

CatalinFetoiu Please remove needs-author-feedback tag and reopen this ticket

CatalinFetoiu commented 1 month ago

sorry, reopening this since we already have logs