SplitWire-Turkey: automating DPI bypass on Windows

What the project automates

SplitWire-Turkey is described as a project for DPI circumvention and tunnelling automation, built specifically for internet users in Turkey. The framing in the documentation is that it is an open source Windows application for performing circumvention without affecting the speed of the internet connection, and that it automatically sets up and manages several circumvention methods from a single interface. That last point is the contribution. The underlying techniques are not invented here. The toolchain named in the documentation includes WireSock, ByeDPI, ProxiFyre, drover, Wgcf and Zapret, and the project is an installer and orchestrator around them. The value is in the wiring: choosing the right combination for the situation, routing only the applications that need it, and making the setup survive a reboot, which the documentation states is the point of installing a service, since you should not have to do anything extra after restarting the computer to reach the affected applications.

Two ways to install, one recommended

The download section offers a setup package and a portable archive, and it recommends the setup package. The setup installer for the current release, 1.5.7, is published on the GitHub releases page as `SplitWire-Turkey-Setup-Windows-1.5.7.exe`, and the documented steps are to download it, run the installation, open the SplitWire-Turkey application, and then follow the usage guides for the method you want. The alternative is the archive, `SplitWire-Turkey-ZIP-Windows-1.5.7.zip`, which you extract to a folder and run `SplitWire-Turkey.exe` from, and the documentation marks that route as not recommended. Both routes carry a note about the Windows SmartScreen warning telling you that Windows has protected your PC, and the instructions are to click More info and then Run anyway, with further notes about the virus scan and that warning given further down the page. That instruction is worth pausing on, because a SmartScreen prompt on an unsigned download is a signal you should evaluate rather than click through reflexively, and the fact that the project asks you to do so is part of what you are accepting when you install it.

The WireSock path and its two variants

The WireSock page describes two installation variants, and the difference between them is which tool handles which traffic. The standard installation puts WireSock 3.4.8.1 and the ByeDPI-Drover combination in place, with text channels tunnelled through ByeDPI and voice channels tunnelled through WireSock. The alternative installation is pure WireSock 3.4.8.1 without ByeDPI or Drover, with all traffic tunnelled directly through WireSock. Both variants include browsers if the option to tunnel browsers as well is switched on. The browser list is named explicitly, covering Chrome, Firefox, Opera, OperaGX, Brave, Vivaldi, Zen, Chromium and Edge, which is a useful detail because browser based clients are the ones people usually forget to route. Once installed, the documentation states that the chosen method starts working automatically on every restart, which is the property that separates a service install from a one-off command.

Tunnelling an application that is not Discord

The WireSock page also covers routing applications beyond the default target, through a folder list. The customise folder list option lets you add the folder where an application you want to tunnel lives, clear the list, run a custom installation that sets up the folder list using Wgcf and WireSock, or create a custom configuration file for the folder list you prepared. That is the mechanism for extending the setup to your own application, and it is a per-application split tunnelling approach rather than a whole machine redirect, which is what keeps the effect on the rest of the system minimal. There is also a scheduled restart option that creates a Windows Task Scheduler job to restart WireSock at intervals, with the documentation advising you to install it only if you are having problems. The advice is a good guide to the tool's own maturity: the features are there, but the author is steering you away from the ones you would otherwise install defensively.

The ByeDPI page and the drover method

The ByeDPI page offers a split tunnelling installation that uses the ByeDPI and ProxiFyre tools to perform DPI circumvention for the Discord application only, with browsers included if the browser tunnelling option is on. There is a second method, the ByeDPI DLL installation, which uses ByeDPI and drover, a DLL hijacking technique, and this one is restricted to the Discord application, with the documentation stating plainly that it does not work for browsers or other programs. A removal action is provided, which uninstalls ByeDPI and deletes the drover files. The documentation also notes a symptom worth knowing in advance: if the Discord application sticks on the Checking for updates screen, the documented remedy is to turn the modem off, wait fifteen seconds, turn it back on, and then restart the computer. The same note appears on both the WireSock and the ByeDPI pages, which suggests it is a common enough failure mode to be worth repeating.

The Zapret path is system wide

The Zapret page is the third method, and the note at the top of it draws the distinction that matters most when you are choosing. The Zapret installations work system wide, and the documentation acknowledges the trade-off directly, saying that although it may not cause a speed loss, it can cause connection problems on some websites and applications. The other two pages carry the opposite kind of note, that their installations work only for the Discord application unless the browser option is enabled. So the choice is between narrow and broad. Zapret covers everything at the cost of possible collateral effects, while the WireSock and ByeDPI routes are scoped to the application you care about plus browsers if you ask for them. A project built around targeted split tunnelling for a specific service is making a different bet from a system wide filter, and the documentation is upfront about which is which.

Where the code lives and who maintains it

The source code is in the `src` directory of the repository, and the documentation states this explicitly, noting that the application is fully open source. The top level of the repository is small and consistent with that: a `.github/` directory holding the workflow files and the alternative language READMEs, a `LICENSE` file, the `README.md`, a `deploy/` directory and the `src/` directory. The README itself exists in four languages, with Turkish, English, Russian and Spanish variants linked by badges, and the naming convention shows the English, Russian and Spanish versions live under `.github/` while the default is Turkish. The project is MIT licensed, which matters here because the tools it orchestrates carry their own terms, and the orchestration code being permissively licensed does not change the terms of WireSock, ByeDPI or Zapret themselves. The release history shows 1.5.7 and 1.5.6 both published on 2026-09-14, with 1.5.5 from 2025-11-26, and the last push was on 2026-09-14.

What the project is not

The limits are structural and worth naming plainly. The first is that this is a Windows application, and the documentation is explicit that it installs a service and requires a restart, so it is not something you will run on a router or on Linux. The second is that it is an orchestrator rather than an implementation, which means the techniques it uses live in other projects, and the version pinning visible in the documentation, such as WireSock 3.4.8.1, is where a break would appear when an upstream tool changes its own behaviour. The third is the SmartScreen instruction, which is a real risk signal for an unsigned installer that asks you to run it anyway, and a careful reader should at least build from source given that the code is published, or at least verify the download before running it. The fourth is scope. This is a targeted circumvention tool for specific applications in a specific network environment, not a general purpose VPN client, and treating it as one would be a misreading of what it does.

Editorial conclusion

SplitWire-Turkey fits a Windows user in Turkey who needs Discord and specific services reachable through a DPI circumvention or split tunnelling method and would rather not assemble the upstream tools by hand, since the app handles the wiring, the scheduled restart task and the per-application routing. It is the wrong choice if you are outside the affected networks, if you need a general purpose VPN rather than a targeted circumvention, or if you are unwilling to run the upstream tools under their own licences, since the app orchestrates other projects rather than implementing the techniques itself. Before you install, read the guide for the method you will use, since the browser tunnelling option changes what each install actually covers, and note the SmartScreen warning applies to the binary. The last push was on 2026-09-14 with release 1.5.7 published the same day, under the MIT licence.

Frequently asked questions

Official sources

1. cagritaskn/SplitWire-Turkey on GitHub
2. Issues
3. License: MIT
4. README
5. Releases