Verified 22.11.2026 (xray 26.7.28 + 26.11.9, matrix of 4 version pairs):
- REALITY authenticates fine both directions ONLY when the client
realitySettings includes "shortId"; without it the server silently
falls back to passthrough ("received real certificate").
- dest www.microsoft.com is broken for REALITY MITM (Microsoft now
serves post-quantum cert chains); www.cloudflare.com / www.apple.com /
www.google.com / download.windowsupdate.com / www.jetbrains.com all work.
- hub transport: expose shortId in summary/payload/uci line; agent reads
uci reality_short_id and emits "shortId" in realitySettings.
NOTE: new tag-form VLESS reverse (Rvs, PR #5101) does NOT register its
control connection when the bridge transport is REALITY on xray >= 26.7
(portal logs show handshake auth OK but no v1.rvs.cool request;
security=none works). See XTLS/Xray-core #6242#6248. Reverse-over-REALITY
e2e therefore blocked pending core-version bisect (26.4.25) or upstream fix.
Upstream ships the router<->hub hop as plain VLESS (tcp, security=none):
UUID-authenticated but cleartext — LuCI credentials and logs inside the
hop are readable by anyone on-path. This fork wraps the hop in
VLESS+Reality (TLS handshake camouflaged against a public dest, no CA
certs, no renewal):
- vps/owrt-remote-hub.py: transport profile (STATE_DIR/transport.json,
x25519 keypair via the xray binary), reality streamSettings in the
server inbound and in make_router_xray_config(), uci transport lines
in the generated OpenWrt config, transport block in heartbeat
hub_update, and xray -test gate before swapping /etc/xray config.
- files/usr/sbin/owrt-remote: security/reality_* uci options,
validation, reality streamSettings in render_client_config,
security-aware compat probe and core-compat checks.
- files/etc/config/owrtremote, cgi form fields, PKG_RELEASE bump.
Env on the hub: OWRT_REMOTE_TRANSPORT=reality|none,
OWRT_REMOTE_REALITY_DEST/FINGERPRINT, OWRT_REMOTE_XRAY_BINARY.
NOTE: xray-core >= 26.9.8 REALITY servers reject client hellos
(XTLS/Xray-core#7259) — pin the hub core to 26.7.28 until upstream fixes it.
Add per-router VPS log archives available offline, live delivery and last reported service state. Keep router logs in RAM with bounded rotation and deduplication. Align log pages and mobile statistics, and bump application and deployment tools to v116.