[Bug/Feature Request] IPv6 UDP (QUIC) routing failure and deadlocks on multi-homed environments when Hyper-V/Virtual Switches coexist with physical WLAN (RFC 6724 / WFP issue)

Open
#42,169 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
cpp, linux

Research direction

The report describes Windows IPv6 routing, UDP/QUIC drops, and WMI/RPC failures with Hyper-V and WSL2 adapters, but it names no WSL source files or tests to start from. First verify which failures WSL can reproduce and isolate; the issue asks for broad Windows networking and service changes, so a done condition needs a narrower scope and owner guidance.

Written by the indexing model from the issue text.

Description

feature wsl2
Environment
  • OS: Windows 11 Pro / Enterprise (x64 / ARM64)
  • Physical Network: Dual-stack campus/enterprise WLAN (Native IPv6 SLAAC/DHCPv6)
  • Virtual Adapters: Hyper-V Default Switch (vEthernet), WSL2 Mirrored/NAT Networking, Wintun
Problem Statement

When a physical wireless interface (WLAN) operates in a dual-stack IPv6 environment alongside Hyper-V/virtual switches (e.g., Default Switch), Windows encounters critical IPv6 routing failures, specifically affecting outbound UDP/QUIC traffic and WMI service stability.

  1. RFC 6724 Default Address Selection Violation & Metric Inversion:

    • The virtual switch vEthernet (Default Switch) binds to a link-local IPv6 (fe80::/64) with an artificially low interface metric.
    • Outbound IPv6 sockets randomly bind to an incomplete/non-routable interface instead of the physical WLAN with a valid global unicast address (240x/260x), triggering instant PING: transmit failed. General failure at the NDIS layer.
  2. WFP (Windows Filtering Platform) Silent UDP Drop:

    • High-throughput, high-port outbound UDP datagrams (RFC 9000 QUIC / HTTP/3) experience silent packet drops or extreme fragmentation failure when crossing virtual adapters, whereas TCP traffic (IPv4/IPv6) passes normally.
    • Mobile operating systems (Linux/Android network stacks) handle multi-homed IPv6 UDP transitions seamlessly under the exact same network conditions.
  3. WMI & RPC Service Deadlocks:

    • Querying network states via Get-NetIPAddress or PowerShell CIMcmdlets frequently crashes with 0x800706be (The remote procedure call failed) due to timeout during interface enumeration across dead virtual adapters.
Reproduction Steps
  1. Connect to an enterprise/university dual-stack Wi-Fi network.
  2. Enable WSL2 or Hyper-V, creating vEthernet (Default Switch).
  3. Attempt high-volume outbound UDP/QUIC communication over global IPv6 endpoints (e.g., benchmark HTTP/3 or QUIC sockets).
  4. Run Test-NetConnection -ComputerName <Global_IPv6_Host> -Port <UDP_Port>.
Expected Behavior
  • Outbound IPv6 UDP sockets should strictly prefer physical adapters with verified Global Unicast Addresses (GUA) and default gateways over internal virtual switches.
  • WFP should not drop outbound UDP datagrams due to multi-homed address ambiguities.
  • WMI network management services (iphlpsvc, winmgmt) should remain robust and non-blocking.
Suggested Improvements for Next Windows OS
  1. Adaptive Metric Deprioritization: Automatically assign a high route metric (e.g., 9999) to internal-only virtual switches for IPv6 GUA destinations.
  2. Robust UDP/QUIC Fast-Path: Modernize the WFP packet scheduler to support mobile-grade UDP multi-homing tolerance.
  3. Zero-Lock WMI Engine: Decouple physical adapter state queries from unresponsive virtual adapter enumeration
Dominant language
C++
Stars
34.4k
Forks
1.9k
Avg merge
1d 23h
Merged PRs (30d)
166

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/WSL

All issues in microsoft/WSL

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.