Version 0.1.0-beta+build.20260824 · released 2026-08-24. TUN (full-tunnel) and proxy mode, on desktop Linux and on router-class ARM hardware, both guarded by an automatic rollback watchdog so a misconfiguration cannot strand the device.
0.1.0-beta+build.20260824 (2026-08-24): Linux & Router • Refreshed the embedded SRSP core with traffic shaping in the production mux write path, cryptographic padding randomness, conservative defaults and bounded backpressure. • TUN/proxy installation and the stacked route/DNS rollback watchdog remain included. • These packages were cross-built on Windows; validate TUN, DNS, routes and rollback on the target Linux/router hardware before production use.
For router-class ARM devices with a conventional Linux userland (plain ip, /dev/net/tun). There is no OpenWrt ipk/UCI/procd package yet — this installer will not appear in your router's own network configuration UI.
Extract the archive for your target and run the installer as root. It asks a few questions (server / SNI / UUID / REALITY key, and Proxy vs TUN) and sets everything up — no manual config editing required.
tar xzf GhostMesh-*.tar.gz
cd <extracted-folder>
sudo ./install.shVerify the archive first: sha256sum -c SHA256SUMS
Updating later: download the newer archive and run its install.sh again — it detects the existing install, keeps your server config untouched, and restarts the service. Check for a newer Beta any time with sudo ghostmesh-safe-enable check-update.
TUN mode redirects this device's default route and DNS through GhostMesh. Two independent watchdogs guard that change — this matters most on a router administered only through the link TUN is about to redirect:
Both remove only what GhostMesh itself added — never your existing default route — so there is nothing risky about running the manual break-glass command at any time:
sudo ghostmesh-safe-enable rollbackProxy mode never touches routing/DNS — it has nothing to roll back, which is why the installer picks it as the default.
— No OpenWrt ipk/UCI/procd/netifd package; routes are managed with plain ip/resolvectl.
— Not yet validated across every ARM router SoC/kernel combination — keep a second way to reach a router (console, LAN cable, a second SSH session) the first time you enable TUN on it.
— No IPv6 transparent proxying in TUN mode; keep OS/browser IPv6 disabled while it's active.