Port forwarding in Rust with TCP and UDP listeners, source-IP allowlists, TLS SNI/ALPN routing, TLS termination, and HTTP/1 and HTTP/2 forwarding. Targets can use TCP or UNIX sockets, round-robin backends, and optional outgoing TLS. Configuration files are watched for reloads.
Documentation: tobaru-rs.github.io for installation, configuration reference, CLI usage, and complete examples.
Native reverse tunnels export named TCP/Unix services from behind NAT through outbound mTLS connections, using ordinary TCP and HTTP routes on the public hub.
The site currently documents dev, not a stable release. Its header links to
the exact source revision. Documentation source lives in docs/
and is published by tobaru-rs.github.io.
Download a binary from GitHub Releases, or build this checkout with Rust 1.88 or newer:
CARGO_BUILD_JOBS=1 cargo install --locked --path .This preserves the pinned HTTP/2 fork's validation fixes. The initial build needs
GitHub access. cargo install tobaru installs an older crates.io release, not
this development revision. See dependency details.
Serve the current directory without a config file:
tobaru static
# Use a different directory, port, and cache lifetime:
tobaru static -p 9000 -c 0 ./distThe default address is 127.0.0.1:8080; -a 0.0.0.0 exposes the directory to
other hosts. Files, including dotfiles, are served without authentication or TLS.
Directories use index.html, with no generated listings. -c sets the
Cache-Control max-age in seconds (default: 3600). See the
static server reference.
Run the self-contained loopback example from this checkout:
tobaru --dry-run examples/first-config.yml
tobaru examples/first-config.ymlThen request http://127.0.0.1:8080/. See the
first-configuration guide,
CLI reference, and
copyable example catalog. The
tracked YAML files are the source of those example pages.
For an existing service on port 9000:
tobaru 'tcp://127.0.0.1:8080?target=127.0.0.1:9000'Use YAML for explicit allowlists, TLS, HTTP routes, and resource limits. Review target precedence and deployment contracts before exposing a listener. A broad raw target permits unmatched TLS; an allowlist on another target does not deny that fallback access.
- Configuration model and IP groups
- Listeners, TCP, and UDP
- Incoming TLS and outgoing TLS
- HTTP routing, actions, and HTTP/2
- CLI and reload, limits, and upgrading
- Tests and documentation development