Connection aggregation

How it works

HypoMux chooses an outbound adapter when each new connection begins. Source-address binding and the Windows interface index keep that connection on its physical path, so independent connections can be distributed across adapters.

Think of it as assigning a path to each new connection—not splitting one connection into pieces. More concurrent requests give HypoMux more opportunities to use multiple networks.

Operating modes

Mode	Best for	Key behavior
System Proxy	Proxy-aware apps such as browsers, IDM, and Steam	Lightweight; can avoid system proxy takeover; does not create a virtual adapter
Virtual Adapter	Broader TCP/UDP and apps that cannot use a proxy	Uses Wintun, WFP, DNS, and routes for system-level routing

System Proxy mode

HypoMux exposes local HTTP/HTTPS and SOCKS5 proxy services and can take over the Windows system proxy. It suits apps that follow the system proxy or allow a local proxy to be configured. It does not create a virtual adapter and is normally the best first choice for downloads.

Virtual Adapter mode

This mode uses Wintun, WFP, DNS, and routing rules to cover broader traffic. It runs safety checks before start. Exit or disable other TUN, VPN, or accelerator tools that already take over the default route.

Speed and latency

Connection aggregation increases combined throughput across concurrent connections. One TCP connection remains limited by its assigned path, and aggregation does not guarantee lower latency. Use direct-routing rules for competitive games, meetings, and voice apps.

WARNING

Aggregation does not create one public IP or turn several lines into a single-link bonding protocol. Do not judge it from a single-connection speed test; use a multi-connection download or several concurrent tasks.