OAF is a parental control software based on OpenWrt. It supports popular applications across gaming, video streaming, instant messaging, such as TikTok, YouTube, Facebook. Currently, it supports hundreds of different applications.
For a detailed introduction, please visit www.openappfilter.com.
- DPI-based protocol identification: Supports Layer 7 protocol parsing and HTTPS domain resolution, and operates independently of DNS.
- Industry-standard architecture: Flow-based identification for high efficiency, with extremely low hardware requirements.
- Supports custom protocol signatures: Offers a high degree of flexibility and customization.
- Supports installation as a plugin on OpenWrt systems: Compatible with all OpenWrt-enabled devices.You can download the plugin package corresponding to your architecture from the releases page.
- Prepare a set of OpenWrt source code that has already been successfully compiled into firmware. (Instructions for compiling OpenWrt source code can be found via independent tutorials and will not be covered here.)
- Clone the OAF source code. Navigate to the root directory of your OpenWrt source code and execute the following command:
git clone https://github.com/destan19/OpenAppFilter.git package/OpenAppFilter
- Enable the OAF compilation options.
Application Filtering consists of three distinct source packages, corresponding to the LuCI App, the service daemon, and the kernel module.
Before compiling, you must enable the build options for these three packages. You can do this by selecting
luci-app-oafvia themake menuconfiggraphical interface. Alternatively, you can enable them by executing the following commands (run from the source code root directory):
echo "CONFIG_PACKAGE_luci-app-oaf=y" >>.config
make defconfig
This will automatically enable the compilation options for all three modules.
- Begin compiling OAF. If you have previously successfully compiled your OpenWrt source code, you can choose to compile only the individual packages:
make package/luci-app-oaf/compile V=s
make package/open-app-filter/compile V=s
make package/oaf/compile V=s
Alternatively, you can recompile the entire firmware image; this will integrate the plug-in directly into the firmware build:
make V=s
The Build ImmortalWrt packages workflow builds this project against the official
ImmortalWrt 25.12.1 SDK. Start it manually from the Actions page and choose one
of these targets:
all: build every supported target.x64: build forx86/64.arm: build for 64-bit ARM usingarmsr/armv8.
Each target produces a GitHub Actions artifact containing the individual APK
packages, SHA256 checksums, build metadata, and a self-extracting .run
installer. The installer checks that it is running on the matching ImmortalWrt
release and target, updates the APK package lists, then installs the bundled
kmod-oaf, appfilter, and luci-app-oaf packages in that order with
apk add --allow-untrusted. Any bundled LuCI translation package is installed
after those three packages:
sha256sum -c SHA256SUMS
sh openappfilter-*-immortalwrt-25.12.1-*.run
The kernel module is tied to the exact ImmortalWrt target and kernel ABI. Do not
use the ARM artifact on other ARM targets such as rockchip/armv8; build a
package for that specific target instead.
https://t.me/openappfilter (Telegram)
If you encounter some issues during installation or usage, you can join the group for discussion(The group was created only recently).
- Individuals can use this software completely free of charge, and are also permitted to develop upon and redistribute it.
- If you undertake derivative development based on OAF, you must adhere to the GPL 2.0 license and retain references to the OAF repository or website information.
- If a company wishes to use this software, please contact the author for authorization.
If you find this project helpful, please give it a star.
