Define rules in one specification (YAML or JSON). The steer core turns it into nftables rules,
routing tables and address sets in a single atomic transaction. Written in C; protocols are
plugins bundled with the core package and installed offline. The management panel with a
service catalog is splify2; the sing-box replacement for
podkop and forkop is steer-box-connector.
- Rules evaluated from top to bottom: select which clients' traffic uses which outbound; the first match wins
- Domains through fake-IP: the resolver returns a synthetic address; the Linux kernel restores the real address through DNAT
- DNS per rule: DoT, DoH (HTTP/1.1, HTTP/2, HTTP/3), DoQ, UDP/TCP, directly or through an outbound, with caching; server groups (parallel or sequential) and a separate server for other sites
- Outbounds and groups: interface, AmneziaWG, subscription tunnel, block;
order,latency,manual,balancegroups;on_failwhen all members fail - Native protocol clients as plugins: VLESS/Reality (Vision, tcp/grpc/xhttp/ws/httpupgrade), hysteria2, trojan, shadowsocks, socks, http, vmess, xsteer, Cloudflare WARP — TCP and UDP, IPv4 and IPv6
- IPv6 routing rules:
family: 4 | 6 | bothon a rule, without leaks outside the outbound - WireGuard over simulated TCP where UDP is blocked
steer fitcompresses a blocklist of hundreds of thousands of prefixes to fit the router- CLI and control socket:
apply,status,diag,explain,plugin, and events for management panels
Download the package for your architecture (DISTRIB_ARCH in /etc/openwrt_release) from
releases or the mirror's
dist branch. There is one package per architecture,
steer-core; protocol plugins (vless, hysteria2, proxy, xsteer, obfs, warpbox, awg)
are bundled and can be installed offline:
apk add --allow-untrusted ./steer-core-<version>-1_<arch>.apk # OpenWrt with apk
opkg install ./steer-core-<version>-1_<arch>.ipk # OpenWrt with opkg
steer plugin list # installed plugins
steer plugin install vless # add a missing protocolUpgrading from 2.0.x removes the old module packages (steer-vless and others, steer-extended)
and installs the plugins needed by the specification's outbounds. The Telegram bridge is the
tgws plugin from splify2-extended-plugins. See docs/guide.md.
/etc/steer/spec.yaml: domains from the list use WireGuard; everything else goes directly:
version: 2
lan: { devices: [br-lan] }
lists:
blocked: { domains_file: lists/blocked.dom }
outputs:
vpn: { kind: interface, device: wg0, on_fail: drop }
rules:
- { name: блоклист, to: [blocked], out: vpn }steer apply --dry-run && steer apply
steer status
steer explain example.orgsplify2.github.io/docs/steer: guide, specification v2, control and events, core architecture, protocols: VLESS, hysteria2, trojan and others, xsteer, WARP, server and hub.
./build.sh # packages for all 11 architectures (STEER_ARCH=<arch> for one); requires Docker
make && make test # build and run tests on the development machineGPL-3.0. Third-party code: libyaml (MIT), wolfSSL (GPL-3.0), and ngtcp2 (MIT, with the
Brutal patch). Versions and checksums are in build/wolfssl/fetch.sh and build/ngtcp2/fetch.sh.