zapret: a standalone DPI circumvention toolkit for OpenWrt routers, now frozen in favor of zapret2
DPI bypass multi platform
At a glance
- What is it?
- bol-van/zapret is a C toolkit that tries to stop deep packet inspection from recognizing blocked HTTP(S), TCP and UDP traffic, without any third-party server. It still receives bug fixes, but its author has moved feature work to zapret2, which changes what a new user should install.
- Who is it for?
- zapret suits someone who already runs it on an OpenWrt router or Linux box and needs it to keep working, since the version still gets bug fixes. A new user should start with zapret2 instead, because this repository accepts no new features.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly C, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- bol-van/zapret16,411 ★ · +245
| Repository | 2026-09-21 | 2026-11-15 |
|---|---|---|
| bol-van/zapret | 16.2k | 16.4k |
245 Stars in the last 55 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
This version is end-of-life and new features go to zapret2
The first thing the README says after a warning about scammers is that this version of zapret is no longer developed. It is in end-of-life mode: no new functions, only bug fixes, and pull requests that add features are not accepted. The current version is zapret2, in the separate bol-van/zapret2 repository. Bug fixes do still land here; the last push was on 4 October 2026, and the latest release, v72.13, came out on 21 July 2026, after v72.12 in March and v72.10 in February. The consequence is plain: an existing install keeps working and gets fixes, but if your provider changes its blocking in a way that needs a new technique, that technique will appear in zapret2, not here.
It prevents the DPI trigger rather than repairing the damage
zapret works by sending traffic that a DPI system does not expect and cannot parse, so the rule that would block a request never fires. The README gives simple examples: splitting an HTTP request into TCP segments so the GET arrives before the rest, writing the Host header in a different case, adding a space after the method, or adding a trailing dot to the host name. More advanced methods work at the packet level.
It distinguishes passive DPI, which reads traffic and injects RST or HTTP redirect packets but cannot drop packets, from active DPI, which sits in the wire and can drop anything in a flow. Against a passive DPI that only injects to the client, iptables rules that drop the RST can be enough. If the passive DPI also sends RST to the server, nothing can be done after the fact. That is why zapret targets the trigger, and why it cannot help once the block has already fired on both sides.
nfqws and tpws are two different engines
The repository builds four programs from nfq/, tpws/, ip2net/ and mdig/. nfqws is the packet-level engine, built around DPI desynchronization: its options cover fakes, fake modification, TCP segmentation, sequence number overlap, IP_ID assignment, IPv6-specific modes, duplicates, a SYNACK mode, a SYNDATA mode, UDP support and IP fragmentation, with multiple strategies and filtering by WiFi network. tpws has its own TCP segmentation, a tlsrec option, MSS settings, other manipulation parameters and multiple strategies of its own. Each has its own iptables and nftables rules. ip2net and mdig are smaller helpers with their own README sections. Flow offloading and hardware quirks get separate sections under nfqws, which tells you router setups need checking before nfqws behaves as expected.
macOS builds without nfqws
The Makefile has separate targets for the default build, systemd, android, bsd and mac, and they do not build the same set. The default list is nfq, tpws, ip2net and mdig, but the mac target uses a shorter list that leaves out nfq. On macOS you get tpws, ip2net and mdig, and none of the packet-level nfqws techniques. That matches the platform list: OpenWrt routers are the main target, traditional Linux, FreeBSD and OpenBSD are supported, macOS only partly, and most functions work on Windows. Every target collects the built binaries into binaries/my and leaves symlinks in each source directory, so a rebuild for another target starts by cleaning that directory.
blockcheck.sh picks parameters for your provider
There is no universal setting. Which trick works depends on the DPI your provider runs, and the README says outright that in Russia active DPI from the TSPU systems is now everywhere, sometimes alongside older DPI boxes still left on, so traffic has to get past several at once. The repository ships blockcheck.sh for testing a provider before choosing parameters, plus install_prereq.sh, install_bin.sh, install_easy.sh and uninstall_easy.sh for the scripted install, config.default, and the init.d/ and ipset/ directories. Domain-based filtering and an autohostlist mode decide which hosts get the treatment. Quick-start guides exist for Linux and OpenWrt in quick_start.md and for Windows in quick_start_windows.md.
Download only from the author, because scammers resell it
The README opens with a warning. zapret is free and open source, and anyone who insists you download it only from their own site, or demands that links, videos or files be removed on copyright grounds, is violating the license in LICENSE.txt. GitHub does not detect that license automatically, so the repository's license field shows as unknown; read LICENSE.txt yourself if licensing matters to you. Voluntary donations to the author are a separate matter and are linked from the README. The README also explains bypassing blocks through a third-party host and argues for buying a VPS, which is the route to consider when local tricks stop working.
Editorial conclusion
zapret suits someone who already runs it on an OpenWrt router or Linux box and needs it to keep working, since the version still gets bug fixes. A new user should start with zapret2 instead, because this repository accepts no new features. It is also the wrong tool where the DPI resets the server side of the connection as well as the client, since zapret can only try to avoid triggering the block. Before installing, run blockcheck.sh against your own provider and fetch the code only from the bol-van repositories.
Frequently asked questions
Is there zapret for Linux?
Yes. zapret supports traditional Linux systems and OpenWrt routers, which are its main target, with a quick-start guide in quick_start.md and a systemd build target in its Makefile.
How do I install zapret?
Follow quick_start.md for Linux and OpenWrt or quick_start_windows.md for Windows. The repository includes install_prereq.sh, install_easy.sh and blockcheck.sh for checking your provider and installing, though new users should consider zapret2, since this version is end-of-life.
How do I install zapret on Windows?
zapret has a separate Windows quick-start guide, quick_start_windows.md. Most of its functions work on Windows.
How do I use zapret on macOS?
macOS support is partial. The mac build target compiles tpws, ip2net and mdig but leaves out nfqws, so the packet-level techniques are not available there.
How do I install zapret on OpenWrt?
OpenWrt routers are zapret's primary target. Start from quick_start.md; the README also has sections on simple installation on OpenWrt and on installing when disk space is very short.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/bol-van-zapret)Star history chart for your README
[](https://hysenlabs.com/projects/bol-van-zapret)Was this useful?