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

Aperta
#42,169 4 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
cpp, linux

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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
Lingua principale
C++
Stelle
34.4k
Fork
1.9k
Merge medio
1g 23h
PR unite (30g)
166

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/WSL

Tutte le issue di microsoft/WSL

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.