-
Notifications
You must be signed in to change notification settings - Fork 826
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
networkingMode=mirrored doesn't work as expected #11090
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:
|
Can you collect logs per these instructions? |
sure @pmartincic, but the whole zip is 88MB large, so ... where should I upload it? Do you want some particular file from inside the zip? |
This comment was marked as duplicate.
This comment was marked as duplicate.
@jfernandz, Does it not let you upload here? |
Max is 25Mb, so I cannot 😞 |
Sorry, I didn't know we had a limit. Send them to the email listed here: https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method |
@jfernandz: See if you're in the same boat as me from this post and the information from J0F3. We had some GPO in our domain that was disabling IPv6 as mentioned by J0F3. When I got rid of the value, networkingMode=mirrored started working and showed the mirrored interfaces for me. We are working internally with the organization to disable this registry GPO that is disabling IPv6 since that's not best practices. |
Thank you so much, I have struggle with this for hours. |
Windows Version
Microsoft Windows [Version 10.0.22621.3007]
WSL Version
2.0.14.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.133.1-microsoft-standard-WSL2
Distro Version
Arch Linux
Other Software
No response
Repro Steps
I've set this values in
.wslconfig
filehowever, when I do:
I can see just the loopback interface is shown:
Expected Behavior
I would expect just with
networkingMode=mirrored
... the output ofip a
shows the very same network interfaces and config than Windows 11.Actual Behavior
As you can see in my pasted output,
ip a
just shows loopback interface, so networking is not available inside WSL.Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: