Skip to content

Keep and officially support networkingMode=bridged, with VLAN ID support #42290

Open

Description

Is your feature request related to a problem? Please describe.

networkingMode=bridged is the only WSL networking mode that is usable for a dedicated-LAN / Hyper-V host setup:

  • Consomme is too slow to be usable. Because every packet is processed in user mode on the host, throughput under sustained traffic is far below what the link can deliver, which rules it out for any real workload.
  • NAT places WSL behind the host on a private subnet with no direct LAN/VLAN presence.

Bridged mode (networkingMode=bridged + vmSwitch=<external switch>) works well on WSL 3.0.3. The utility VM gets its own MAC, DHCP lease (via WSL's built-in dhcpcd), and full switch throughput. However:

  1. It is undocumented on learn.microsoft.com and has previously been removed and reinstated (2.5.6: "Bring back bridged networking mode"), so there is no assurance it will remain. If bridged mode were removed, the remaining options (Consomme/NAT) would not be viable replacements.
  2. There is no way to assign a VLAN ID to the WSL VM's switch port. Set-VMNetworkAdapterVlan cannot be used because the WSL utility VM is not exposed to Hyper-V management, and tagging inside the distro does not work because the port is untagged/access by default (see Add support to specify VLAN # when using Bridged Network Mode #13665).

Describe the solution you'd like

  1. Keep networkingMode=bridged as a supported, documented mode and do not deprecate it.
  2. Add a VLAN setting for the bridged endpoint, e.g.:
    [wsl2]
    networkingMode=bridged
    vmSwitch=WSL-LAN
    vmSwitchVlanId=60
    Internally this could be applied as an HNS VLAN endpoint policy when BridgedNetworking creates its ephemeral HCN endpoint (it currently only sets PortName/Firewall policies).
  3. Document the bridged-mode DHCP timeout setting so it can be tuned for switch ports that take a few seconds to forward.

Describe alternatives you've considered

  • VLAN interface / netplan inside the distro: fails. The WSL port is untagged, and distro network managers (NetworkManager/netplan) conflict with WSL's own dhcpcd and strip the address from eth0.
  • Current working workaround: dedicate a physical NIC to an external vSwitch (no management OS), and on the physical switch set that port to untagged VLAN 60 with PVID 60, with the firewall uplink tagged VLAN 60. This works, but ties the entire NIC to a single VLAN and moves configuration out of the host.

Additional context

Activity

  1. github-actions commented on Nov 16, 2026

    @github-actions
    Contributor

    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 script will output the path of the log file once done.

    If this is a networking issue, please use .\collect-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues

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

    See Collect WSL logs (recommended method).

    If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

  2. pujk-compkickers-personal commented on Nov 16, 2026

    @pujk-compkickers-personal
    Author

    /feature

  3. github-actions commented on Nov 16, 2026

    @github-actions
    Contributor
    Diagnostic information
    Found '/feature', adding tag 'feature'
    
  4. pujk-compkickers-personal commented on Nov 16, 2026

    @pujk-compkickers-personal
    Author

    An additional reason bridged mode needs to stay supported: Consomme is not only too slow, it has also been unreliable across releases. After updating to WSL 3.0.5, Consomme networking broke on this host, and I had to repeatedly reinstall 3.0.3 to get networking working again. (Possibly related: #42223, which reports a Consomme regression from 3.0.3 in 3.0.5.)

    Bridged mode avoided this entirely and has been stable, which is why it should not be deprecated: it is the only dependable option for this setup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions