# zapret-openwrt: OpenWrt Packages for the zapret Anti-DPI Utility > zapret-openwrt packages the zapret Anti-DPI utility for OpenWrt and includes a LuCI application. It suits router administrators who need packaged integration, although the README delegates installation details to a wiki. **remittor/zapret-openwrt** — OpenWrt packages of https://github.com/bol-van/zapret - Repository: https://github.com/remittor/zapret-openwrt - Stars: 1,406 · Forks: 78 - Language: JavaScript - License: MIT - Published: 2026-10-16 · Updated: 2026-10-16 · Language: en - Canonical page: https://hysenlabs.com/projects/remittor-zapret-openwrt ## Why zapret-openwrt Targets OpenWrt Routers zapret-openwrt addresses a packaging and distribution problem for router administrators. The repository description calls it "OpenWrt packages of https://github.com/bol-van/zapret," and its top-level layout places package-related content in `zapret/`. A separate `luci-app-zapret/` directory indicates that the project also includes an application intended for the OpenWrt LuCI interface. This makes the repository relevant to administrators who run OpenWrt locally and want zapret represented through OpenWrt packages. The README is direct about the product category: "Zapret is not a VPN! Zapret is an Anti-DPI utility!" That distinction matters when selecting software. A VPN typically provides a routed or tunneled connection through a remote service, while this repository packages a utility described as an Anti-DPI tool. The README does not describe traffic routing, encryption, remote servers, account systems, or privacy guarantees, so it would be incorrect to attribute VPN properties to the project. The intended user is therefore an OpenWrt administrator rather than a subscriber purchasing a hosted network service. The repository does not document supported OpenWrt releases, target processor architectures, minimum storage requirements, or specific LuCI versions. Those compatibility details cannot be inferred from the directory names. They need to be checked in the installation wiki or release assets before installation. The README also points readers to Zapret Manager for installation and configuration. That is a separate project. The README does not establish whether Zapret Manager installs these release packages, uses another installation route, or provides only a management interface. zapret-openwrt should not be described as dependent on Zapret Manager based on that link alone. Its documented installation entry point is the repository's wiki. ## Package Layout and Release Scope The repository has a compact top-level layout: `.github/`, `LICENSE`, `README.md`, `luci-app-zapret/`, and `zapret/`. That separation is the clearest documented evidence of its organization. `zapret/` is the package-oriented area named after the upstream utility, while `luci-app-zapret/` is a distinct LuCI application area. The README does not expose individual build scripts, service startup commands, firewall rules, or configuration files, so it does not support a more detailed account of the internal data flow. The release list covers two named upstream products or package lines. It includes `v72.20260307` with the description `zapret v72.20260307`, plus `v0.9.20260307` with the description `zapret2 v0.9.20260307`. An earlier listed release is `v72.20260226`. The naming shows that the repository publishes more than one versioned line. It does not explain whether `zapret` and `zapret2` can coexist, whether one replaces the other, or how the LuCI application chooses between them. GitHub Releases serve as the download page, according to the README. That makes release contents more important than the short README when selecting an installation file. The README does not list asset filenames, processor architecture variants, signatures, checksums, or dependency metadata. A router administrator cannot determine from the README which artifact belongs on a particular device. Selecting an asset only by project name could produce a package for the wrong architecture. Automatic updates, rollback, removal, configuration persistence, and restoration of an earlier release are also absent from the README. Those omissions matter for router software because installation can affect services available during boot and connections passing through the router. The missing documentation does not prove that the features are unavailable, but it does mean users must verify them before relying on them. ## Installing Through the Linked OpenWrt Wiki The README provides no installation commands or package configuration. It directs users to the repository wiki under the label "Instructions for installing" and separately recommends Zapret Manager for installation and configuration. Because the README gives no exact command syntax, environment variables, ports, or configuration keys, this review cannot reproduce an operational installation procedure without adding undocumented details. A practical first step is to open the repository's installation wiki, select its procedure for the router's OpenWrt version and processor architecture, and compare those instructions with the assets attached to the intended GitHub Release. GitHub Releases are the repository's stated download page. These compatibility checks should happen before changing a production router because the README does not document a rollback command, backup procedure, or recovery image workflow. After installation, the LuCI application represented by the `luci-app-zapret/` directory is the relevant first interface to inspect. The README does not document its menu path, available controls, generated files, or required settings. It would therefore be inaccurate to claim that opening a named page, enabling a specific toggle, or applying a documented preset restores connectivity. This short tutorial is bounded by the documentation that zapret-openwrt actually provides. The project links an installation wiki, identifies GitHub Releases as its download location, and points to Zapret Manager as another installation and configuration option. Package-selection syntax and the first configuration action remain delegated to those linked sources. ## Anti-DPI Behavior Without VPN Claims The principal behavior identified by the README is Anti-DPI handling. No packet sequence, network hook, protocol filter, or traffic transformation algorithm is documented there. The review therefore cannot explain how individual packets move through the router or which specific techniques are enabled. Although the repository topics include `nfqws`, the README does not explain that component's role in an installed configuration, so assigning it a particular processing stage would go beyond the documentation. This uncertainty matters for network administrators. An Anti-DPI utility is not interchangeable with a VPN, and the README emphasizes that distinction. Installing these packages does not, on the documented evidence, create an encrypted tunnel, select a remote exit location, hide traffic from every network observer, or reproduce the service model of a commercial VPN. Users whose requirements include those properties need software whose documentation explicitly describes them. The project also should not be treated as a universal repair tool for broken connections. The README does not identify supported blocked services, protocols, DPI implementations, or router configurations. It provides no troubleshooting matrix and no documented method for determining whether a routing, DNS, certificate, firewall, or Anti-DPI condition caused a failure. A problem in one of those other layers may require configuration that this repository does not address. OpenWrt administrators who specifically need the upstream zapret Anti-DPI utility packaged for their routers are the clearest audience. Users who need DNS repair, encrypted transport, policy routing, or remote access should inspect those requirements separately rather than assuming this package line supplies them. ## Zapret Manager and Upstream zapret Are Different Routes The README identifies two related but distinct destinations. One is Zapret Manager at `https://github.com/StressOzz/Zapret-Manager`, which the README recommends for installation and configuration. The other is the upstream zapret repository at `https://github.com/bol-van/zapret`. zapret-openwrt packages that upstream project for OpenWrt, whereas Zapret Manager is presented as a separate setup and management option. The visible difference is distribution context. zapret-openwrt is the OpenWrt packaging repository and includes the `luci-app-zapret/` directory. The upstream zapret repository is the source named by the packaging description, but the README does not establish that it provides the same OpenWrt packages. Zapret Manager is recommended as a tool for installing and configuring zapret, but this README does not document its interface, supported routers, or relationship to a particular zapret-openwrt release. zapret-openwrt is the more direct fit when the requirement is explicitly an OpenWrt package set from this repository. The upstream project is the relevant source when the requirement concerns zapret itself rather than this OpenWrt packaging layer. Zapret Manager may suit administrators who want to follow its separate configuration workflow, but the README does not justify claims that it is simpler, more compatible, or more actively supported. The comparison must remain narrow. The README supports distinguishing packaged OpenWrt delivery, upstream source, and a separate manager. It does not contain enough evidence for a broader product ranking. ## Maintenance, Release Cadence, and MIT Licensing The repository is not archived, and its last push was on 2026-08-06. That is a recent recorded change, but recency by itself does not establish OpenWrt compatibility, release quality, or operational reliability. A meaningful maintenance assessment also requires checking whether a release provides an artifact for the intended OpenWrt version and processor architecture, and whether users have a documented way to recover from an unsuccessful installation. The README addresses none of those verification steps in detail. The release list includes versions dated 2026-03-07 and 2026-02-26. Both `zapret` and `zapret2` appear in the listed release set, indicating packaging for separate named lines. Users can select among GitHub Release assets, but the README does not state the upgrade policy, explain whether one release supersedes another, or confirm whether packages can be upgraded in place. The documented release history is therefore more useful for locating versions than for predicting upgrade compatibility. The repository uses the MIT license. Engineers should read the complete `LICENSE` file before modifying or redistributing the project, and should also check for any package-specific notices. This review does not provide legal advice. The license identifier identifies the repository's declared licensing approach, but it does not substitute for reviewing the actual terms attached to a release. Before an upgrade, the relevant check is concrete: compare the target OpenWrt version and processor architecture with the repository wiki and release contents. If that match cannot be established, the package should not replace a working router configuration without additional documentation. ## Conclusion OpenWrt administrators should consider zapret-openwrt when they specifically want packaged access to the zapret Anti-DPI utility and a LuCI application. Users seeking a VPN or a self-contained setup guide should first verify the linked installation wiki and release artifacts. The concrete adoption check is whether the release contains packages and LuCI components suitable for the target OpenWrt device. ## FAQ ### Is zapret-openwrt a VPN? No. The README states, "Zapret is not a VPN! Zapret is an Anti-DPI utility!" The repository packages zapret for OpenWrt rather than documenting a VPN service. ### Where can I find the installation instructions for zapret-openwrt? The README links to the repository wiki under "Instructions for installing." It also points to Zapret Manager as a separate option for installation and configuration. ### Does zapret-openwrt include an OpenWrt LuCI application? Yes. The repository contains the top-level `luci-app-zapret/` directory. The README does not document the application's menu path, settings, or configuration workflow. ## Sources - [Issues](https://github.com/remittor/zapret-openwrt/issues) - [License: MIT](https://github.com/remittor/zapret-openwrt/blob/zap1/LICENSE) - [README](https://github.com/remittor/zapret-openwrt/blob/zap1/README.md) - [Releases](https://github.com/remittor/zapret-openwrt/releases) - [remittor/zapret-openwrt on GitHub](https://github.com/remittor/zapret-openwrt) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/remittor-zapret-openwrt