-
Notifications
You must be signed in to change notification settings - Fork 834
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
Cannot enable Mirrored network on WSL #11154
Comments
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:
|
Hi. Can you please collect networking logs by following the instructions below? |
I have finished it in the title “Diagnostic Logs” of the first answer. |
Is there a available solution yet, please? I found in the Microsoft documentation that it might mean HCN_E_REQUEST_UNSUPPORTED error which is "The specified request is unsupported". I am hosting my virtual machine in azure, hope this helps! |
Hi there. can you clarify what version of Windows is running in your virtual machine? Is this a server SKU? is it a headless server SKU? I'm reading code where it looks like it's blocking it for some reason. |
It's Windows Server 2025 Datacenter Azure Edition Build 26052 running on Microsoft Azure, I connect to it by RDP. So I think it is a Headless server SKU |
Yeah, sorry. I found code in another component that's blocking Mirrored mode from running on Server SKUs :( I'm going to try and fix this for the next release. I will have to pitch this to folks who work on servicing for existing releases. |
Hi @keith-horton , just a friendly ping to see if you were able to get Mirrored mode working with Windows Server (2022 in particular) and if there's any eta on the release for the next WSL pre-release build. Thanks! |
I'm also getting this on Windows Datacenter Server 2025 preview. |
I have settled with port forwarding for now as detailed in #4150 Hopefully this constraint is removed for Windows Server SKUs soon. |
Still exists on Windows Server VNext Preview (Canary) - Build 26280 |
Still getting this on Windows Server 2025 Version 24H2 Build 26100.2033. |
Same. I'm hoping to run an up-to-date squid version under WSL, but in NAT mode, all requests logged are comming from the default-gateway of the WSL subnet instead of the true client, so there is no distinction between requests. (it's not only DNAT-ting on the Windows host, but also SNAT-ting) really was hoping that Mirrored Network mode would solve this for me. |
Windows Version
Microsoft Windows [Version 10.0.26052.1000]
WSL Version
2.1.1.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.146.1-microsoft-standard-WSL2
Distro Version
Ubuntu 18.04
Other Software
No response
Repro Steps
I set the network type to mirrored in the .wslconfig file.
networkingMode=mirrored
and then restart WSL
Expected Behavior
Everything's getting good. It should work.
Actual Behavior
When I start wsl it reports an error:
Diagnostic Logs
WslNetworkingLogs-2024-02-14_17-09-15.zip
The text was updated successfully, but these errors were encountered: