sing-box Fork Expands from Desktop VPN Launcher to Android and Router Deployments
The sing-box-lx project, an actively maintained fork of sing-box, has completed its transition from a desktop VPN engine to a unified platform running on Android devices and OpenWrt routers. The developer behind L×Box and Sing-box Launcher reports more than 1,700 commits, 24 stable 1.14 releases, and roughly seventy specialized builds since June.
Two major protocol additions stand out. A native MASQUE outbound implements CONNECT-IP as defined in RFC 9484, tunneling complete IP packets rather than UDP datagrams and reusing the same userspace network stack employed by WireGuard endpoints. The implementation treats Cloudflare WARP as a configuration preset while keeping device registration outside the core. AmneziaWG 2.0 received exhaustive verification against amneziawg-tools, the upstream kernel module netlink interface, and live IPC round-trips, confirming parity on all sixteen obfuscation parameters including Jc/Jmin/Jmax junk packets, S1–S4 padding, H1–H4 magic headers, and I1–I5 signature packets.
Android required extensive runtime optimizations. A full state machine now suspends idle WireGuard and AmneziaWG endpoints, sometimes destroying userspace devices entirely, and restores them lazily on first use. Health checks skip cycles when recent traffic has succeeded. The resulting savings reach 31 percent lower resident set size and 80 percent lower kernel CPU usage on production configurations. Additional fixes eliminated 127-second TCP dial timeouts caused by unbounded gVisor SYN backoff and ensured prompt recovery after Android Doze cycles.
Several long-standing silent failures were resolved during the summer. A three-byte change restored REALITY compatibility after Xray 26.7.11 began enforcing minimum client versions. XHTTP path handling now correctly appends trailing slashes, and mutual uplink/downlink deadlock in packet-up scenarios was eliminated. XMUX connection reuse and automatic TLS record fragmentation for detoured outbounds were also added.
The newest component, sing-box lxd, is a headless daemon that hosts the core and exposes a persistent gRPC management channel. Designed for routers, it survives configuration reloads, validates candidates before apply, performs automatic rollback on failure, and delivers the same structured observability previously available only to Android clients. An additional REST endpoint aggregates DHCP leases, ARP tables, bridge FDB entries, hostapd data, and operator labels to map IP addresses to human-readable device names.
Releases continue to follow three self-imposed rules: drift from upstream is measured by merge-base rather than commit count, every submodule is integrity-checked before merge, and no stable tag is cut without execution on real hardware. Static musl binaries for router architectures, including big-endian MIPS, are published alongside detailed OpenWrt recipes for isolated VPN SSIDs.
Related articles
AmneziaWG Container for MikroTik Routers Delivers Top Performance Six Months After Launch
A developer released an AmneziaWG container for MikroTik devices in February 2026 and has since added major improvements in speed, protocol support, and stability. The lightweight container leverages the router's native WireGuard implementation for cryptography while handling AmneziaWG obfuscation in software. Performance now reaches 250-350 Mbit/s on models such as Hap Ax3 and RB5009B after switching to C code and increasing buffer sizes with RouterOS 7.24. New features include server mode for connecting multiple MikroTik devices, random port hopping, IPv6 support, dynamic DNS, and offline configuration. The project survived an early GitHub ban caused by test scripts and has grown to over 370 stars while remaining fully offline and privacy-focused.
Building Resilient DoH Failover on MikroTik RouterOS to Handle Unreachable Cloudflare Responses
A network administrator encountered a persistent issue in a branch office where pages like Tailwind CSS CDN failed to load despite valid DNS responses from Cloudflare DoH. The problem stemmed from unreachable IP addresses such as 8.6.112.0 and 8.47.69.0 returned by the resolver, which RouterOS treated as healthy because it only checked for valid IP types rather than route reachability. RouterOS supports only a single active DoH upstream via the use-doh-server parameter, requiring custom scripting for failover between multiple endpoints like Cloudflare and dns.google. The solution involved static DNS entries for bootstrap addresses, certificate trust anchors including SSL.com TLS ECC Root CA 2022, and a health monitor script that probes using DNS-JSON API calls instead of switching the resolver directly. Multiple iterations addressed issues like cache-based false positives, plain DNS fallback risks from provider spoofing, and clock validation to prevent certificate failures. The final implementation uses thresholds for failure and recovery to avoid flapping and ensures post-switch verification before committing to a backup endpoint.
NetRuleRouter Alpha Released to Route Traffic Across Multiple Connections Without Disabling VPN
Developer krox1 has released the first public alpha of NetRuleRouter v0.1.0-alpha.1 for Windows and Linux, a local network policy manager that distributes traffic between primary and secondary connections based on domains, IP ranges, applications, and subnets. The tool emerged from practical issues that intensified after Russian authorities discussed VPN restrictions in March 2026, with operators and platforms later prompting users to disable VPN for domestic services. NetRuleRouter sits on top of existing connections rather than acting as a VPN client or proxy, allowing users to keep corporate VPNs, personal VPNs, and direct internet active simultaneously. It supports seven matching methods including exact domains, wildcard subdomains, CIDR ranges, and application paths, with priority rules to resolve overlaps and built-in leak protection that prevents protected destinations from falling back when the secondary connection drops. The alpha includes diagnostic tracing, preset rule sets for Russia and other regions, import/export capabilities, and a first-run wizard that configures the background service and initial bindings. Limitations around DNS, shared IPs, and brief startup windows are documented, and the project explicitly does not protect against account-level blocks by services such as Anthropic.
Setting Up Nextcloud Talk on TrueNAS with Custom Domain for Private Family Calls
A detailed guide explains how to deploy Nextcloud Talk on a TrueNAS server behind a custom domain to create a self-hosted messaging and calling platform for family use. The author addresses problems with commercial messengers such as VK notifications failing on iOS and Telegram requiring VPN connections. The solution uses HestiaCP on a VPS for reverse proxying, Let's Encrypt SSL certificates, and port forwarding on a home router to reach the TrueNAS instance at 192.168.0.17:30027. Additional steps cover configuring coturn for TURN relay to enable reliable voice and video calls, updating trusted domains in Nextcloud, and disabling router DoS protection. The setup also enables Screen Sharing, reactions, and push notifications while keeping all data under user control.