No interfaces in Ubuntu when using networkingMode=mirrored #11002
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:
|
|
If it helps, I've tried Ubuntu 22.04 as well, and have flipped between a few wsl versions including 2.0.9 and 2.0.15 pre-release on top of what I'm testing now with the newest non-pre-release. I and a few other engineers with our company are unable to make this networkingMode=mirrored setting work without watching all of our interfaces get clobbered. I have completely uninstalled all of WSL and kernels, as well as features like Hyper-V, Virtual Machine Platform and Windows Subsystem for Linux and started all over with a basic |
|
Hi. Can you please collect networking logs by following the instructions below? |
|
I already did when I posted this issue initially and sent them to the email address indicated in my post. I was requested not to post the logs directly to here by my company's InfoSec team. They were emailed to [email protected] as indicated in your link already. |
|
@craigloewen-msft can you share the logs? |
|
Checking back in again to see if there is anything further that I can provide. We had another ticket put in where around 15 people from a couple other departments are dealing with this and the number of reported impacted users is increasing. I did take another opportunity to purge all things related to WSL2 / Hyper-V / Virtual Machine Platform from my system and then re-install with "wsl --install" once rebooted and back. There must be some residual settings or something else that keeps impacting this. I took the opportunity to update to the latest 2.1.0.0 release as well, but that made no difference. I did take an opportunity to look at my Windows "System" event viewer log and there are around 80 entries getting logged every 30 seconds connected to the "Hyper-V-VmSwitch" and "VfpExt" sources. The events show NICs and vSwitches being created and deleted repeatedly with a friendly name of "FSE HostVnic". I cannot find much about what this is. Let me know if there is any further log information that I can provide. |
|
@chanpreetdhanjal I just emailed over additional WSL logs generated from collect-wsl-logs.ps1 to go along with the ones collected by collect-networking-logs.ps1 |
|
It has been well over a week since last response to this issue. Are there additional details that I can provide to work towards resolution? We have a large number of engineers affected by this still. People are using various workarounds in the interim (either falling back to WSL1, not ideal, or keeping networkingMode set to NAT and running a workaround PowerShell script to adjust route metrics on the host workstation to get around imposed full VPN tunnel routes). |
|
I am not getting the messages. @craigloewen-msft can you please pass along the logs and details? @erik-spigle-payroc our team is on it and we will get back to you as soon as we have an update for you. Thanks! |
|
Thanks for checking back in. If there is another secure means to send the logs over, I'm happy to pursue another avenue to do-so. Thanks. |
|
Nope we have the logs now. |
|
@chanpreetdhanjal: Any thing new about this issue? I can reproduce the issue reliable when disabling IPv6 according to this guide: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/configure-ipv6-in-windows (by setting the Registry Key Windows Version: 10.22631.3007 - Windows 11 23H2 @erik-spigle-payroc: Maybe you have a similar configuration? |
|
@J0F3: I am seeing the same value in my registry. Now I am wondering if at one point in time our organization was doing something to disable IPv6 (some legacy GPO or the like that may no longer exist). I will compare a bit against one of our newer machines that is not having problems using |
|
@J0F3: You, my friend, may be a huge lifesaver here. We are still internally testing with others, but I found that users who have no issues only have the |
|
@erikspigle-payroc 😄 👍🏻 |
|
"When IPv6 is disabled through the Registry Key" - I'm suspecting this is the reason that it's not showing up. I think HNS (which WSL uses to create endpoints through vswitch) requires/assumes both IPv4 and IPv6 interfaces. @J0F3 : is IPv6 required to be completely unbound? |
|
I did want to circle back and say we had done some more pilot testing with those who are affected, and we had set the Otherwise, I think we can consider my issue resolved. It may not hurt to update documents regarding |
|
@erikspigle-payroc , thank you for confirming! |
|
@keith-horton Unfortunately not. The reason why I cam across this was because my company wants to disable IPv6 completely on the clients because IPv6 connections would bypass the force-tunneling VPN (because the VPN connection is not IPv6 capable). But I think also that the issue can be considered as resolved because we found the root cause of the issue.
So WSL with mirror networking mode seems then to be on of that components which I think is perfectly fine. 😊 |
|
@J0F3 . Thanks. Just FYI, I tested WSL with mirroring enabled after disabling IPv6 with the only known supported way that I know of - using Powershell to disabling the v6 binding: Set-NetAdapterBinding -Name Wi-Fi -ComponentID ms_tcpip6 -Enabled $false (just replace "Wi-Fi" with the name of the interface you want to modify - as reported by "Get-NetAdapter") After running the above and rebooting (sadly, we need a reboot for our FSE driver to see the binding change), WSL continued to work great, and v6 addresses were not assigned. |
|
@J0F3 , could you share the registry value you are changing? I'll look to add to our WSL documentation for v6 support. |
|
@keith-horton: I am fairly sure he's referring to the information he linked to previously: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/configure-ipv6-in-windows Location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters By default, In our case, a prior systems engineer, who is no longer at our company, had created a group policy to apply this REG_DWORD with a value of 0xFF (hex) and deployed it to all workstations. Once we determined that this was the culprit, and we didn't feel there was a compelling reason to have IPv6 fully disabled, we updated the group policy to change the value to 0x20 (hex) or 32 (decimal) to re-enable IPv6, but to prefer IPv4 over IPv6. This worked for us. I'm not sure what setting to the other documented values would do, but the safest tested options on our end are a value of 0 or 0x20 (hex), which both leave IPv6 enabled and thus allow |
|
@keith-horton Yes, @erikspigle-payroc is absolutely right. I was referencing the
Thx! |
|
Hi there, I'd just like to add to the conversation, because I've had a similar issue which I was able to resolve. I'd just activated mirrored networking in my Ubuntu 24.04 instance and then applied the following [wsl2]
networkingMode = mirrored
dnsTunneling = trueAfter rebooting the instance: no interfaces were found. In this post, IPv6 was mentioned, so I enabled it via the Settings app on my Ethernet and now: I have more interfaces than ever before. Maybe this will help someone in the future, although I also feel this is a bug that is potentially caused by my Insiders build. Windows version info: |
|
Is there a way to limit or sellect what interfaces that are mirrored ? I first tried to use the bridged mode, My initial intended usage was to have multiple "distros" (clones of ubuntu 22.04) with individual network combinations and tools installed, runnimg as individual (isolated from the host) similar to a linux container) Maybe wsl is not the tool I need.. Is there another way than using Docker? or full Hyper-V virtualization? Best regards, |
|
@Anders-Fromell-ITxPT , mirroring is "on or off" -- internally, network adapters get mirrored, then WSL creates a network device in Linux for those networks. Mirrored mode today only supports a single WSL instance :( |
@keith-horton, thanks for the clarification.. Best regards, |
Windows Version
10.0.22621.2861
WSL Version
2.0.14.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.133.1-1
Distro Version
20.04
Other Software
N/A
Repro Steps
%UserProfile%\.wslconfig
When I connect to our corporate network via GlobalProtect VPN client, which was recently re-configured from split-tunnel to full-tunnel VPN, I have no Internet (whereas it works fine while disconnected). When not using the above networkingMode=mirrored, connectivity to the Internet does not work due to GlobalProtect taking priority over all routes on the host workstation. Anything like "sudo apt update" or other things that will hit the Internet will fail. DNS resolution works just fine with the "dnsTunneling=true" setting set to true and all lookups work fine.
Once I set "networkingMode=mirrored" in the .wslconfig file, all interfaces within the Ubuntu VM disappear except for the "lo" interface. I and several others in our organization are seeing the same thing. We do have one individual in the organization that seems to be operating fine with "networkingMode=mirrored", but we have been unable to determine what is different about this individual's configuration.
Expected Behavior
With "networkingMode=mirrored", I would expect to see my host workstation interfaces mirrored into my Ubuntu instance.
Actual Behavior
All interfaces except "lo" get removed when "networkingMode=mirrored" is configured.
Diagnostic Logs
Have emailed to [email protected]
The text was updated successfully, but these errors were encountered: