Application-scoped Ethernet and Wi-Fi connection mixing for Windows.
C#
2
50 commits
updated Oct 7, 2026
DualLink applies two independent internet links to new TCP connections made by selected Windows applications. It is designed for launchers and browsers that open several parallel download connections.
Download the latest offline installer from GitHub Releases. It includes the required runtime, local filter, and driver. Verify the included SHA256SUMS.txt before running it.

Normal Windows routing stays unchanged for apps you do not select. For selected apps, each new IPv4 TCP connection is assigned to Ethernet or Wi-Fi. Both shares new connections equally, Safe keeps destinations on a consistent link after a short startup period, and Backup uses Ethernet first. Speed limits are independent of the mode.
For one large file, use multiple chunks when the host supports them so separate connections can use both routes. A single ordinary TCP connection cannot be split across two internet links without a remote bonding endpoint.
The Details drawer checks both routes, DNS, route independence, and filtering in plain language. Technical activity stays hidden until requested. App choices can be changed during a boost without closing established downloads.



DualLink only filters processes the user selects. The desktop interface runs with normal user permissions; Windows asks for administrator approval only when the user enables boosting. Its elevated local helper owns packet-filter changes and the local proxy, which listens only on loopback, uses fresh random credentials for each run, and is not exposed to the LAN. Disarming or exiting restores the previous local-filter configuration. An independent watchdog also restores that configuration if the interface or helper exits unexpectedly. Adapter changes are detected automatically; an available route continues carrying new sessions while another reconnects. Turning a route off affects new connections immediately while established ones finish normally.
One TCP connection cannot be split across two links without a remote aggregation server. The speed benefit comes from distributing the multiple connections opened by launchers and browsers. Live game traffic is intentionally not a target.
DualLink routes IPv4 TCP. Its explicit filter rule blocks selected-app IPv6 so applications can fall back to IPv4; an IPv6-only destination cannot work through this mode. UDP, including QUIC and most live game traffic, is outside the routed path. Open means the app process exists, not that it is sending routed traffic. Link byte counts are the evidence of actual use.
The detection catalog includes Steam, Epic Games, Riot Games, Battle.net, EA app, JDownloader, Chrome, Edge, Firefox, Brave, Opera, Internet Download Manager, and Free Download Manager. Registrations, known folders, or a running executable must provide an existing path. Portable or unusual installations can be added manually. Detection is not a certification that every app version or server benefits from dual-link routing.
See the project audit and implementation and validation record for the current fixes, benchmark, and outstanding live validation.
Upload results may combine less visibly than downloads. Speed tests often reuse a small number of long-lived connections for upload, and mobile hotspots usually have much lower upstream capacity. DualLink reports live upload use per route so you can see which links are contributing.
Developers need Windows 10/11 x64, the .NET 10 SDK, and Inno Setup 6. Run build.ps1 to restore, test, publish, generate the SBOM and checksums, and create the offline installer. The exact three public assets are placed in dist\release; other files under dist are internal build outputs. See the release policy and compliance review before distributing a build.
DualLink is released under AGPL-3.0-only. Review the privacy statement, security policy, third-party notices, and release compliance review. Release executables are currently unsigned; verify the published SHA-256 checksums before running them.
Application-scoped Ethernet and Wi-Fi connection mixing for Windows.
C#
2
50 commits
updated Oct 7, 2026
DualLink applies two independent internet links to new TCP connections made by selected Windows applications. It is designed for launchers and browsers that open several parallel download connections.
Download the latest offline installer from GitHub Releases. It includes the required runtime, local filter, and driver. Verify the included SHA256SUMS.txt before running it.

Normal Windows routing stays unchanged for apps you do not select. For selected apps, each new IPv4 TCP connection is assigned to Ethernet or Wi-Fi. Both shares new connections equally, Safe keeps destinations on a consistent link after a short startup period, and Backup uses Ethernet first. Speed limits are independent of the mode.
For one large file, use multiple chunks when the host supports them so separate connections can use both routes. A single ordinary TCP connection cannot be split across two internet links without a remote bonding endpoint.
The Details drawer checks both routes, DNS, route independence, and filtering in plain language. Technical activity stays hidden until requested. App choices can be changed during a boost without closing established downloads.



DualLink only filters processes the user selects. The desktop interface runs with normal user permissions; Windows asks for administrator approval only when the user enables boosting. Its elevated local helper owns packet-filter changes and the local proxy, which listens only on loopback, uses fresh random credentials for each run, and is not exposed to the LAN. Disarming or exiting restores the previous local-filter configuration. An independent watchdog also restores that configuration if the interface or helper exits unexpectedly. Adapter changes are detected automatically; an available route continues carrying new sessions while another reconnects. Turning a route off affects new connections immediately while established ones finish normally.
One TCP connection cannot be split across two links without a remote aggregation server. The speed benefit comes from distributing the multiple connections opened by launchers and browsers. Live game traffic is intentionally not a target.
DualLink routes IPv4 TCP. Its explicit filter rule blocks selected-app IPv6 so applications can fall back to IPv4; an IPv6-only destination cannot work through this mode. UDP, including QUIC and most live game traffic, is outside the routed path. Open means the app process exists, not that it is sending routed traffic. Link byte counts are the evidence of actual use.
The detection catalog includes Steam, Epic Games, Riot Games, Battle.net, EA app, JDownloader, Chrome, Edge, Firefox, Brave, Opera, Internet Download Manager, and Free Download Manager. Registrations, known folders, or a running executable must provide an existing path. Portable or unusual installations can be added manually. Detection is not a certification that every app version or server benefits from dual-link routing.
See the project audit and implementation and validation record for the current fixes, benchmark, and outstanding live validation.
Upload results may combine less visibly than downloads. Speed tests often reuse a small number of long-lived connections for upload, and mobile hotspots usually have much lower upstream capacity. DualLink reports live upload use per route so you can see which links are contributing.
Developers need Windows 10/11 x64, the .NET 10 SDK, and Inno Setup 6. Run build.ps1 to restore, test, publish, generate the SBOM and checksums, and create the offline installer. The exact three public assets are placed in dist\release; other files under dist are internal build outputs. See the release policy and compliance review before distributing a build.
DualLink is released under AGPL-3.0-only. Review the privacy statement, security policy, third-party notices, and release compliance review. Release executables are currently unsigned; verify the published SHA-256 checksums before running them.