A process connection event, an Ethernet frame and a virtual network interface answer different questions. Choosing the wrong boundary can produce a plausible-looking diagnostic that never measured the thing you needed.
This is a maintainer-side guide to five TitanCSA Windows networking projects, prepared with autonomous AI assistance. It compares their public documentation as read on 15 November 2026. It is not a new benchmark, security audit or installation test.
Start with the question
| Question | Project | Boundary to keep in mind |
|---|---|---|
| Which process and endpoint appeared at a connection stage? | Connection Trace Studio | WFP lifecycle metadata, without packet contents |
| What Ethernet bytes reached a selected adapter's filter? | Packet Capture SDK | Bounded NDIS observations, affected by offloads and truncation |
| Which local rule matched a connection authorization? | Titan Network Filter | Ordered ALE rules and attributed decisions |
| How does my UDP client handle controlled loss or delay? | Network Emulation SDK | One process and remote IPv4/UDP endpoint |
| How can my application exchange Ethernet frames with Windows? | Virtual Network Adapter SDK | A separate virtual adapter owned by the application |
For the three observation and policy tools
The earlier networking observation-layer guide covers Connection Trace Studio, Packet Capture SDK and Titan Network Filter in detail, including their offline preview commands. Read that guide for lifecycle gaps, captured lengths and policy-generation attribution.
This companion focuses on the two remaining integration boundaries: deliberately impairing a UDP flow and creating a virtual Ethernet endpoint. Neither is established merely by observing a connection or frame.
Impairment: keep the scope visible
Network Emulation SDK handles ordinary outbound UDP/IPv4 for one selected process and destination. TCP, IPv6 and inbound traffic pass unchanged. Start a fresh UDP socket after first enabling the policy or changing its process/endpoint scope.
The delay queue is bounded to 128 retained packets. Overflow passes through and increments a counter; those packets can overtake delayed ones. Queue behavior and reinjection errors belong in test results. This is not a bandwidth limiter, a VPN failure simulator or a guarantee of delivery timing under CPU pressure.
Virtual networking: the adapter is only one component
Virtual Network Adapter SDK exposes one software Ethernet interface with a 1500-byte MTU and a 64-frame outbound queue. Queue saturation drops new frames. Its advertised 1 Gbit/s link speed is a software property, not a throughput measurement.
The example leaves physical adapters, DNS, gateways and bridges unchanged. Your application must implement addressing, protocol handling and any transport it needs. Creating the interface does not create a VPN, configure routes or provide a remote tunnel.
Two proposed checks with different success criteria
For a UDP impairment fixture, first record a baseline with a fresh socket and known endpoint. Enable a chosen policy, open a new socket in the target process, then record the application's observations alongside the SDK's matched, dropped, delayed, overflow and reinjection counters. Counters are cumulative for the driver lifetime; take before/after differences. An accepted reinjection is not confirmed delivery to the peer. Queue overflow deserves a separate case because pass-through can overtake delayed packets.
For a virtual-adapter integration, make the direction explicit in your code: Receive() removes a frame Windows sent to the application; Send() supplies a frame back to Windows through the virtual adapter. An empty receive queue is not a disconnected link. Handle the empty-queue result without busy-polling, and inspect connection state separately. After device removal or restart, authorize and connect again; do not silently resend a failed frame.
These are proposed evaluation checks based on the documented contracts. They have not been run as part of this article.
A practical first evaluation
Begin with each project's labelled --preview where documented, then review its matching release and prerequisites before an explicit live test on an authorized system. SDK packages and driver installation are separate steps.
The access models also differ. Connection Trace Studio and Titan Network Filter document evaluation binaries without a technical trial timer. Network Emulation, Packet Capture and Virtual Network Adapter use product-specific, per-handle permissions lasting at most one hour, with explicit renewal. Do not transfer the input-driver kernel-boot demo model to these networking tools.
Public application/SDK source is MIT licensed; evaluation-driver source and prebuilt binaries have separate terms. Microsoft signing does not establish WHQL certification or universal Windows 11/HVCI compatibility. Consult the selected project's validation notes for the configurations actually qualified.
For a proposed test, write down the target process/adapter, IPv4 or IPv6, transport, expected failure and counters you will inspect. Keep proposed checks separate from results you actually obtained.
Exact SDK package names and installation guides | All 58 public projects by workflow
Top comments (0)