स्क्रीनशॉट
इस ऐप के बारे में
मूल विवरण अंग्रेज़ी में हैAndroid SOCKS5 TUN tunnel client — routes the device's entire network traffic through a remote SOCKS5 server using a TUN virtual interface. No root required. Features: - User-space TCP state machine forwarded via SOCKS5 CONNECT - UDP / DNS / QUIC relay via SOCKS5 UDP ASSOCIATE (UDP-in-UDP or UDP-in-TCP 0x04) - Remote DNS (fakedns) with fake IPv4 (198.18.0.0/15) and fake IPv6 - IPv4 + IPv6 dual-stack support - Per-App routing modes: Global, Allowlist, or Exclusion - Auto-reconnect with exponential backoff on connection drop - Live traffic statistics (up/down bytes & session count) in persistent notification - Custom primary & secondary DNS servers - Start tunnel on boot - Quick Settings tile for one-tap tunnel toggle - Multiple profile management with JSON export/import via clipboard - Native C (epoll) engine + JNI + Kotlin UI Privacy notes: - While the tunnel is up, the proxy server's hostname is re-resolved outside the tunnel (needed to follow DDNS / IP changes without tearing the TUN interface down). That lookup is sent to the DNS servers of the network the tunnel actually runs over. The custom DNS servers above are used only as a fallback when that resolver gives no answer, and the fallback is written to the log. - With Remote DNS enabled, DNS queries from apps are relayed to the proxy exit instead of being answered locally. Open source (MIT), reproducible builds.
APK संस्करण
APK फ़ाइलें मूल रिपॉज़िटरी से मिलती हैं।
संस्करण में बदलाव
- Fixed: every closed TCP session left one socket behind in CLOSE_WAIT. `detachFd()` hands the native layer a duplicate of the socket's descriptor, and the cleanup path only asked the Java side to close its copy — the native copy was never closed. After four IP changes this reached 501 leaked sockets, each holding a descriptor. Both copies are now closed
SHA-256 चेकसम
caf0a91d021c1159486e12b1d3b9863534d9e6b87b90343b4f311aee1cee231eसंस्करण में बदलाव
- Fixed: rotating the screen no longer reconnects the tunnel. The main screen used to rebuild itself on a rotation and re-run "connect on open", so after you pressed Stop, turning the device brought the tunnel back up. A rebuilt screen is now treated as the same session and no longer auto-connects - Fixed: "start tunnel on boot" now also requires that the tunnel was still running when you shut down. Previously it only checked the checkbox, so a Stop you pressed was silently undone at the next bo
SHA-256 चेकसम
ab7cbadd1bcdb4e82d82863ec5a2e6f0c8441a54019d48d34ce6a33f6bf7a85fसंस्करण में बदलाव
- Fix: a DNS query carried over TCP (remote DNS enabled, with the query itself sent through the tunnel) was never released. The connection record and its buffer stayed allocated, and the session counter only ever went up. After 512 of them the client would refuse every new TCP connection — DNS and ping still worked, everything else was dead, and restarting the tunnel brought it back. The session now releases itself as soon as the answer has been written back, and a regression test asserts the se
SHA-256 चेकसम
26eeeb94fb92eef12daaa97f196bca1dcb622d76e71287f7efee7de736758a62
