Skip to content
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

No network device when mirrored network is enabled #11423

Closed
1 of 2 tasks
ArslanTu opened this issue Apr 5, 2024 · 3 comments
Closed
1 of 2 tasks

No network device when mirrored network is enabled #11423

ArslanTu opened this issue Apr 5, 2024 · 3 comments

Comments

@ArslanTu
Copy link

ArslanTu commented Apr 5, 2024

Windows Version

Microsoft Windows [Version 10.0.22631.3374]

WSL Version

2.1.5.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.146.1-2

Distro Version

Ubuntu-22.04

Other Software

No response

Repro Steps

  1. Add such config to .wslconfig
[wsl2]
networkingMode=mirrored
  1. wsl --shutdown then wsl
  2. ifconfig output is like this:
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 76  bytes 6824 (6.8 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 76  bytes 6824 (6.8 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

There is no eth0 or other device, no matter there is or no proxy in windows.
Remove config above just works well.

Expected Behavior

There exist some network devices other than lo when mirrored network is enabled.

Actual Behavior

There is no network device other than lo when mirrored network is enabled.

Diagnostic Logs

No response

Copy link

github-actions bot commented Apr 5, 2024

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

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!

Open similar issues:

Closed similar issues:

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

@ArslanTu
Copy link
Author

ArslanTu commented Apr 5, 2024

I have solved this with the help of this issue.
Just open regedit and chang the value of DisabledComponents (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\) from 0xFF to something else, like Decimal 32. Then reboot and enjoy it.
Reference

@OneBlue
Copy link
Collaborator

OneBlue commented Apr 5, 2024

Closing since the issue is resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants