Big update for VX6: Windows 11 and Windows Server 2022+ are now in the mix on both AMD64 and ARM64.
This isnβt just a βit builds on Windowsβ moment β the platform layer now detects whatβs available at runtime and picks the best path automatically. βοΈ
π§ What landed
πͺ Windows transport selection
π MsQuic integration with TCP fallback
π§ eBPF/XDP capability detection
β‘ AF_XDP ring interface for packet I/O
π Go-based performance CLI with JSON / text / CSV output
π₯οΈ Native Win32 performance GUI
π οΈ Build support for Windows AMD64 and ARM64
π§© Why this is interesting
The goal was to keep VX6 flexible across platforms without turning Windows into a special-case mess.
So instead of assuming a feature is always there, VX6 now checks at runtime:
Is MsQuic available? β use it
Not available? β fall back to TCP
Is eBPF/XDP present? β expose it
Not present? β keep going with userspace paths
That makes the stack more adaptable and keeps the behavior predictable across environments.β¦