sing-box

LxBox Evolves from VPN Client to Comprehensive Network Traffic Management Ecosystem

LxBox has grown from a personal Android client for sing-box into a full ecosystem spanning mobile, desktop, and router platforms. The project now supports a wide range of VPN and proxy protocols within a single routing framework, allowing users to manage corporate SSL VPNs, home WireGuard connections, and proxy servers together. Key security features include default ingress blocking to prevent unauthorized reverse connections through VPN tunnels and protections against traffic leaks via excluded applications. The developer introduced progressive configuration levels, from one-click WARP setup to advanced JSON editing and AI-friendly documentation. The core sing-box-lx fork ranks among the top sing-box derivatives and powers third-party tools such as the upcoming NekoBox 6. LxBox is available on Google Play, F-Droid, and GitHub, with desktop launcher support for Windows 7 and later, macOS, and Linux.

Six Months After tun0 Leak: Which Android VPN Clients Fixed Server Address Exposure and Which Ignored It

A detailed investigation reveals that Android VPN clients suffer from two distinct server address leaks when split tunneling is enabled. The first leak, tied to an unprotected local SOCKS proxy on 127.0.0.1, was quickly mitigated by most Xray and sing-box based clients through random ports and passwords. The second, more persistent leak allows excluded applications to bind sockets directly to the tun0 interface and discover the VPN server IP without root or special permissions. Only TeapodStream and OlConnect implemented owner-UID checks using ConnectivityManager.getConnectionOwnerUid, yet both initially mishandled the INVALID_UID response returned for excluded apps. AmneziaVPN has unmerged pull requests that correctly reject unknown owners, while sing-box offers a manual package_name_regex rule. v2rayNG closed the report as not planned, and major clients including WireGuard for Android, Mullvad, Proton VPN and others have issued no statements.

sing-box Fork Expands from Desktop VPN Launcher to Android and Router Deployments

The sing-box-lx fork has grown from a desktop-focused VPN engine into a cross-platform solution supporting Android and headless router deployments. Over 1,700 commits since June produced 24 stable 1.14 releases and dozens of specialized builds. New protocol support includes a full MASQUE CONNECT-IP outbound for Cloudflare WARP and a rigorously verified AmneziaWG 2.0 implementation matching 16 obfuscation parameters across three reference sources. Android adaptations introduced aggressive endpoint state management that reduced RSS by 31 percent and CPU load by 80 percent while fixing long-standing TCP dial timeouts inherited from gVisor. The new lxd headless daemon exposes gRPC observability and admin REST endpoints with mTLS, config validation, automatic rollback, and device-name mapping for OpenWrt deployments. All changes follow strict upstream discipline: minimal patches, regular rebases, reproducible builds, and real-device testing before stable tags.

Configuration Drift Silently Breaks Multi-Hop Chains in sing-box Reality Fleet

A post-mortem analysis of a censorship circumvention network using sing-box and Reality revealed that four out of seven nodes were unreachable due to outdated allowlists, even though all monitoring reported green status. The fleet consisted of 14 endpoints across seven machines and four providers, with traffic routed in two hops where entry nodes only knew client identities and exit nodes only knew destinations. White-list rules on entry nodes permitted only five addresses instead of all required relays, causing urltest to silently discard most chains without logging failures. Canary checks, external probes, and the relay-lockdown.sh script all passed because none compared the allowlist against the full signed configuration. Two private paid nodes lacked any route section entirely, exposing them to potential abuse. The issue stemmed from configuration drift over time, with no single person maintaining an overview of the entire system. Automated fixes were implemented with safeguards to prevent fleet-wide lockouts.

Free VPNs Fail Within Days as Russian Filters Detect Tunnels Without Decrypting Traffic

Free VPN services promoted in Telegram now stop working after just a few days, with Instagram Reels freezing, YouTube stalling in endless loading, and Google Gemini returning 403 errors. Modern Russian content filtering systems have advanced beyond simple IP blocking and can identify proxy tunnels through indirect traffic characteristics such as packet sizes, inter-packet intervals, and TLS handshake structures. A common failure pattern involves connections succeeding initially before data transfer abruptly slows or drops after roughly 16 KB, a behavior linked to deep packet inspection recognizing proxy patterns. Users and developers counter these detections with techniques including packet fragmentation, reduced TCP segment sizes, and tools like zapret to desynchronize analyzers while preserving normal server-side flow. Services such as sing-box employ uTLS to better mimic legitimate browser TLS fingerprints, while ShadowTLS v3 and padding methods help mask connections as ordinary HTTPS sessions to allowed resources. Recommended working options include AmneziaVPN, Cloudflare WARP, Red Shield VPN, and self-hosted setups on Xray or sing-box, though some claims around hynet.cloud lack independent verification.

Why Simple VPNs No Longer Suffice Against Advanced DPI Blocking Telegram, Reels and Google AI Studio

Over the past year or two, users have observed that free VPNs and Telegram proxies often stop working after a few days, with Reels freezing, YouTube failing to load, Telegram stuck on Connecting, and Google AI Studio or Gemini returning errors. Modern filtering systems now analyze traffic behavior such as packet sizes, timing intervals, and TLS handshake characteristics rather than decrypting content. Techniques like TCP desynchronization via nfqws, MSS clamping with iptables, uTLS fingerprint emulation in sing-box, and ShadowTLS v3 for borrowing legitimate sessions are being deployed to evade detection. Padding is added to encrypted streams to reduce entropy and frustrate statistical shaping by TSPU systems. Commercial and self-hosted options including hynet.cloud, AmneziaWG, Red Shield VPN, GoodbyeDPI, and Cloudflare WARP each present distinct advantages and limitations when facing evolving network restrictions.