AsteriskNG

July 12, 2026 · View on GitHub

Telegram Channel

VPN Service, TPROXY(ROOT), TUN2SOCKS(ROOT), and BPF2SOCKS(ROOT) run modes support
VMess, VLESS, Trojan, Shadowsocks, Socks, HTTP, Hysteria2, WireGuard, strategy group, and chain proxy support
v2rayNG, mihomo subscription format support
Resource file management for geoip.dat, geosite.dat, geoip-only-cn-private.dat, and the Xray executable
ROOT start-on-boot script generation through Magisk service.d
Native ROOT network monitoring for dynamic local-address bypass, system IPv6 control, and IPv6 tethering
MIUIX Compose UI

Screenshot 1 Screenshot 2 Screenshot 3 Screenshot 4

Requires root permission.
Runs the local Xray executable directly with libsu.
Uses hev-socks5-tunnel to create the fixed TUN device asterisk0.
Uses Xray's local SOCKS5 inbound as the tunnel target.
Shares most ROOT routing and app proxy behavior with TPROXY, but routes traffic through the TUN device instead of Xray's TPROXY inbound.

Requires root permission and eBPF support from the Android kernel.
Runs the local Xray executable and the native bpf2socks helper directly with libsu.
Uses cgroup eBPF programs to redirect local TCP connections and UDP datagrams to the BPF2SOCKS bridge, then forwards them to Xray's local SOCKS5 inbound.
Does not create a TUN device. The default bridge port is 65532, and the default SOCKS5 inbound port is 65534.
Requires its eBPF probe to pass before startup. This mode cannot start when device support is insufficient.

All ROOT modes use the native asteriskd monitor after Xray and mode rules are ready.
It tracks local IPv4/IPv6 address changes and atomically refreshes direct-bypass iptables chains or BPF maps, so public addresses are not accidentally captured by the proxy path.
When system IPv6 disabling is enabled, it also applies the setting to newly appearing IPv6 interfaces. With IPv6 enabled, it reacts to configured tethering interfaces and removes Android IPv6 TC offload rules when needed.
The monitor log is files/xray/logs/asteriskd.log; generated files/xray/stop.sh is the single ROOT stop entry point and restores captured IPv6 state before cleanup.

Runtime files are stored in the app private files/xray directory, commonly /data/user/0/org.asterisk.zcc.ang/files/xray.
The bundled Xray executable is restored from native libraries and can be replaced manually with an xray executable file or a zip archive containing xray.
geoip.dat and geosite.dat can be restored from bundled assets, updated from online sources, or replaced manually.
Built-in update sources include Loyalsoldier/v2ray-rules-dat, v2fly/geoip, v2fly/domain-list-community, Chocolate4U/Iran-v2ray-rules, and runetfreedom/russia-v2ray-rules-dat.

Initialize submodules before building:

git submodule update --init --recursive

Open the project root in Android Studio, or build it with Gradle wrapper:

.\gradlew.bat assembleDebug

On macOS or Linux:

./gradlew assembleDebug

The build:

uses the Android SDK and NDK
downloads or prepares the bundled Xray-core asset
checks out hev-socks5-tunnel to ProjectConfig.HEV_SOCKS5_TUNNEL_VERSION before building it
builds the native hev-socks5-tunnel JNI library and CLI runtime from the vendored submodule
builds the native asteriskd, bpf2socks, and setuidgid helpers
packages native runtime components for arm64-v8a, armeabi-v7a, x86, and x86_64

If Gradle cannot find Android NDK, set ndk.dir in local.properties, set ANDROID_NDK_HOME, or install an NDK under the Android SDK.

For WSA, VPN permission can be granted with:

appops set org.asterisk.zcc.ang ACTIVATE_VPN allow