No interfaces in Ubuntu when using networkingMode=mirrored

[erikspigle-payroc]

Windows Version

10.0.22621.2861

WSL Version

2.0.14.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.133.1-1

Distro Version

20.04

Other Software

N/A

Repro Steps

%UserProfile%\.wslconfig

[wsl2]
networkingMode=mirrored
dnsTunneling=true

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 wsl-gh-logs@microsoft.com

[github-actions]

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:

• No network access with networkingMode=mirrored (#10791), similarity score: 0.83
• Mirrored networking mode is not supported (#10823), similarity score: 0.81

Closed similar issues:

• networkingMode: mirrored not working but virtioproxy does. (#10717), similarity score: 0.70

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

[erikspigle-payroc]

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 wsl --install to start fresh, but to no avail.

[chanpreetdhanjal]

Hi. Can you please collect networking logs by following the instructions below?
https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues

[erikspigle-payroc]

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 wsl-gh-logs@microsoft.com as indicated in your link already.

[chanpreetdhanjal]

Craig Loewen (@craigloewen-msft) can you share the logs?

[erikspigle-payroc]

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.

[erikspigle-payroc]

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

[erikspigle-payroc]

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).

[chanpreetdhanjal]

I am not getting the messages. Craig Loewen (@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!

[erikspigle-payroc]

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.

[chanpreetdhanjal]

Nope we have the logs now.

[J0F3]

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 DisabledComponents to 0xFF)
When IPv6 is disabled through the Registry Key and networkingMode=mirrored is set in .wslconfig then in WSL the loopback interface is the only interface available.

Windows Version: 10.22631.3007 - Windows 11 23H2
WSL Version: 2.0.14.0
Distro Version: Ubuntu 22.04

@erik-spigle-payroc: Maybe you have a similar configuration?
At least the GlobalProtect VPN in Full/Force Tunneling Mode is one thing we have both im common.

[erikspigle-payroc]

Jonas Feller (@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 networkingMode=mirrored.