[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)
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
- Domain
- networking, operating-systems
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
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.
-
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 failureat the NDIS layer.
- The virtual switch
-
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.
-
WMI & RPC Service Deadlocks:
- Querying network states via
Get-NetIPAddressor PowerShell CIMcmdlets frequently crashes with0x800706be (The remote procedure call failed)due to timeout during interface enumeration across dead virtual adapters.
- Querying network states via
Reproduction Steps
- Connect to an enterprise/university dual-stack Wi-Fi network.
- Enable WSL2 or Hyper-V, creating
vEthernet (Default Switch). - Attempt high-volume outbound UDP/QUIC communication over global IPv6 endpoints (e.g., benchmark HTTP/3 or QUIC sockets).
- 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
- Adaptive Metric Deprioritization: Automatically assign a high route metric (e.g., 9999) to internal-only virtual switches for IPv6 GUA destinations.
- Robust UDP/QUIC Fast-Path: Modernize the WFP packet scheduler to support mobile-grade UDP multi-homing tolerance.
- 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
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/WSL
-
feature wsl2
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
microsoft/WSL#42306 · 3 comments ·
Maintainers usually reply within 1 day
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microsoft/WSL#42114 · 3 comments ·
Maintainers usually reply within 1 day
-
feature kernel wsl2
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/WSL#41107 · 3 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
feature kernel
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
microsoft/WSL#41054 · 9 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
feature GPU
Difficulty 1/5 1-3 hours Newbie friendliness 70/100
microsoft/WSL#13592 · 4 comments ·
Maintainers usually reply within 1 day
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
nextcloud/passman-android#214 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
2026.11.0 fails to install on Intel macOS: requirements.txt pins cryptography==50.0.2 for Darwin x86_64May be free again A pull request for this issue was closed without being merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 87/100
esphome/esphome#22892 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
distante/esphome-components#50 · 1 comment ·
Maintainers usually reply within 1 day
-
arch-based hyprland
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
noctalia-dev/noctalia#5423 ·
Maintainers usually reply within 1 day