OpenFlux: Research Tool for TCP Tunneling Over Pluggable Transports
Explore OpenFlux, an open-source research tool that tunnels TCP packets across non-standard pluggable transports including Yandex Docs cursor messages and WebRT
Developed by open-source developer p1neappleXpress, OpenFlux is an open-source network stack research tool that applies the pluggable transports mechanism to TCP tunneling architectures. Designed for protocol researchers and systems engineers, it explores how unconventional application-layer communication channels can be repurposed for reliable packet delivery.
Image source: p1neappleXpress via GitHub
As modern traffic analysis and protocol inspection systems grow increasingly sophisticated, researchers are actively investigating alternative abstraction layers to decouple data transport from rigid transport-layer assumptions. OpenFlux approaches this problem experimentally by encapsulating raw TCP payloads within familiar, high-level collaboration and real-time communication events.
Pluggable Transports and Unconventional Communication Channels
At the core of OpenFlux is a modular pluggable transports architecture designed to swap low-level transport mechanisms without altering client-side application contracts.
While traditional network tunneling relies on well-known VPN tunnels or standard TLS sessions that are easily cataloged by firewalls, OpenFlux experiments with everyday application behaviors that blend into standard web traffic patterns. The primary transport mechanisms currently implemented include:
- Yandex Docs Cursor Messages: Real-time cursor coordinates and collaborative synchronization events within Yandex Docs are utilized as an active packet carrier, shuttling encapsulated TCP data across collaborative document sessions.
- WebRTC DataChannel (Max): Real-time peer-to-peer WebRTC DataChannels are leveraged to deliver low-latency bidirectional data exchange between endpoints.
By channeling encapsulated TCP traffic through these unconventional mediums, OpenFlux demonstrates how non-traditional carriers can maintain data flow under restrictive network inspection environments.
System Architecture and Multi-Platform Build Targets
The complete OpenFlux transmission pipeline is structured into a clean four-stage topology designed for clear separation of concerns.
The end-to-end data flow operates as SOCKS5 Client → Transport Layer → Exit Node (universal-bypass-tool) → Internet. A local client connects to the OpenFlux SOCKS5 interface, where outbound requests are intercepted and packaged into the configured transport channel. Upon reaching the remote side, an exit node powered by universal-bypass-tool reconstitutes the encapsulated stream and forwards standard TCP requests to the public internet.
From an engineering perspective, OpenFlux is developed in Go, utilizing Go 1.26.3 or higher for native server and desktop compilation. It also features cross-platform build support for multiple operating environments:
- Desktop and Server Targets: Native binary compilation powered by Go 1.26.3+ for high-throughput packet handling.
- Mobile Targets: Support for Android NDK builds and iOS Xcode project targets, allowing researchers to evaluate mobile client scenarios.
- Open-Source License: Released under the GNU General Public License v3 (GNU GPLv3), encouraging open peer review and extensible protocol research.
Research Scope and Operational Precautions
OpenFlux is explicitly designed as a non-commercial open-source research instrument for evaluating network stacks and protocol dynamics.
The author notes that the project provides no guarantees for production circumvention, firewall evasion, or sustained platform compliance. Relying on external third-party services—such as Yandex Docs or WebRTC infrastructures—for non-standard transport carries significant operational risks, including account suspensions or automated IP throttling by service providers.
Consequently, security researchers and network engineers should restrict all testing and evaluation to controlled lab networks or isolated testing environments, using OpenFlux strictly as a tool for academic and structural protocol discovery.
Sources
The complete source code, architectural specifications, build configurations, and GNU GPLv3 license terms for OpenFlux are available directly on the official GitHub repository for researchers and developers interested in pluggable transport exploration.