repowisep1neapplexpress/openflux

Architecture of p1neapplexpress/openflux

p1neapplexpress/openflux is 349 source files holding 3,429 symbols across 16 modules, written mainly in Go, PHP, JavaScript. The largest module is transport, with 141 files, and 9 files are entry points into the dependency graph.

How openflux fits together

main.go is the program entry point, and its --role flag selects whether the binary runs as a client or an exit node. On the client, the tunnel/ directory provides the virtual network interface that captures traffic, and --inbound selects a SOCKS5 proxy or a tun interface. The transport/ directory implements each native and scripted transport together with the session manager, which can run several transports at once and fail over between them. The exit node uses one of the two backends in tunnel/, selected with --mode: l3 forwards raw TCP and UDP with SNAT and DNAT on Linux as root, while l4 terminates connections in a gVisor userspace stack and re-dials the real server. The share/ directory turns shareable links that carry a full client configuration into JSON-ready results, and deploy/ holds the VDS installer script and the sources of the PHP exit.

Largest modules

  • transport: 141 files and 28,023 lines of code
  • root: 32 files and 4,222 lines of code
  • tunnel: 31 files and 3,998 lines of code
  • mobile: 30 files and 3,509 lines of code
  • deploy: 26 files and 4,566 lines of code
  • provision: 15 files and 3,191 lines of code
  • ios-app: 8 files and 574 lines of code
  • share: 6 files and 793 lines of code

Languages

By file count: Go 257 files, PHP 18 files, JavaScript 12 files, Shell 12 files, Swift 6 files, C++ 2 files.

Documentation

Repowise documents openflux in 395 pages generated from the source, 26 of them written explanations of the repository and its modules. Module guides include:

  • network: Checksum and Formatting
  • tunnel/l3: L3 Backend Routing
  • utils: Logging and Secrets

More on openflux: summary and FAQ, codebase overview, code health.