ssh-tunnel-gateway 0.3.0

SSH tunnel server + agent with reverse port forwarding

ssh-tunnel-gateway

Single Python package that ships both the server and agent CLIs.

Project Description

ssh-tunnel-gateway provides a gateway server (ssh-tunnel-server) and an agent (ssh-tunnel-agent) for reverse SSH access to hosts that are not directly reachable from clients.

The server manages control-plane registration over HTTP and allocates a tunnel port (port_b).
The agent establishes and maintains the SSH reverse tunnel data plane to that allocated port.

Design Philosophy

• Use a public gateway host as a bastion to reach private/internal servers that do not expose inbound SSH.
• Use standard SSH as the transport layer for mature security properties and operational reliability.
• Stay native to SSH workflows so teams can integrate with existing clients, keys, config files, and ProxyJump.
• Keep control-plane logic minimal: HTTP API only for registration, identity, and lease lifecycle.

Usage (Start Here)

Server foreground:

API_KEY="change-me" ssh-tunnel-server

Server systemd mode:

API_KEY="change-me" ssh-tunnel-server -d

Agent foreground:

ssh-tunnel-agent --api-key change-me --endpoint http://server:12000

Agent systemd mode:

ssh-tunnel-agent -d --api-key change-me --endpoint http://server:12000

Notes:

• Server auth supports either API_KEY (single key) or API_KEYS (comma-separated multiple keys).
• Restarting ssh-tunnel-server does not restart active SSH tunnels; existing tunnels stay up as long as the underlying SSH session to gateway sshd remains alive.
• If --agent-id is not provided, agent generates a UUID once and caches it locally for future restarts.
• Agent writes current session info (including port_b) to ${STATE_DIR}/session.json by default.
• Server reuses the same port_b for the same agent_id when possible.
• If the previous port is busy, server tries to reclaim (kill listener on that port) and reuse it.
• If reclaim fails, server rotates to a new free port.
• Default reverse bind host is 0.0.0.0 (public bind on gateway).
• Use --reverse-bind-host 127.0.0.1 if you want loopback-only bind for strict bastion usage.
• If not set, agent follows the server-provided reverse bind host.
• In -d mode, register/startup failures exit immediately so systemd can restart the unit.

Install

On the gateway server host:

pip install ssh-tunnel-gateway

On each agent host:

pip install ssh-tunnel-gateway

Quick Start (ProxyJump)

1. On the gateway server host, start server:

API_KEY="change-me" ssh-tunnel-server

Or with multiple API keys:

API_KEYS="key1,key2,key3" ssh-tunnel-server

With default public reverse bind (AGENT_REVERSE_BIND_HOST=0.0.0.0), gateway sshd_config must include:

• AllowTcpForwarding remote
• GatewayPorts clientspecified

2. On the agent host, start agent:

ssh-tunnel-agent --api-key change-me --endpoint http://<gateway_host>:12000

3. Get port_b from the agent side:

• Foreground mode prints a log line with port_b.
• Foreground logs also print:
  • ssh_user: tunnel login user returned by server.
  • jump_user: ProxyJump user returned by server.
  • agent_user_hint: defaults to local $USER on the agent host.
• Session file is always written to ${STATE_DIR}/session.json (default ./data/session.json):

cat ./data/session.json

Get only port_b:

python3 -c 'import json; print(json.load(open("./data/session.json"))["port_b"])'

4. Add user SSH config (~/.ssh/config):

Host GWServer
    HostName <gateway_public_ip_or_dns>
    User <gateway_ssh_user>
    Port 22

Host AgentServer
    HostName localhost
    User <agent_ssh_user>
    Port <port_b_from_agent_session_json>
    ProxyJump GWServer

5. Connect:

ssh AgentServer

Systemd Usage

Server unit (/etc/systemd/system/ssh-tunnel-server.service):

[Unit]
Description=ssh-tunnel-gateway server
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
User=gw-tunnel
WorkingDirectory=/opt/ssh-tunnel
EnvironmentFile=/etc/ssh-tunnel/server.env
ExecStart=/usr/local/bin/ssh-tunnel-server -d
Restart=always
RestartSec=5

[Install]
WantedBy=multi-user.target

Example server env (/etc/ssh-tunnel/server.env):

API_KEY=change-me
# Or multiple keys:
# API_KEYS=key1,key2,key3
SERVER_PORT=12000
SSH_USER=gw-tunnel
SSH_JUMP_USER=li
SSH_PUBLIC_HOST=gateway.example.com
AUTHORIZED_KEYS_PATH=/home/gw-tunnel/.ssh/authorized_keys
AGENT_REVERSE_BIND_HOST=0.0.0.0

Agent unit (/etc/systemd/system/ssh-tunnel-agent.service):

[Unit]
Description=ssh-tunnel-gateway agent
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
User=root
WorkingDirectory=/opt/ssh-tunnel
EnvironmentFile=/etc/ssh-tunnel/agent.env
ExecStart=/usr/local/bin/ssh-tunnel-agent -d
Restart=always
RestartSec=5

[Install]
WantedBy=multi-user.target

Example agent env (/etc/ssh-tunnel/agent.env):

API_KEY=change-me
API_URL=http://<gateway_host>:12000
SSH_HOST=<gateway_host>
SSH_PORT=22
LOCAL_TARGET_HOST=127.0.0.1
LOCAL_TARGET_PORT=22

Enable and start:

sudo systemctl daemon-reload
sudo systemctl enable --now ssh-tunnel-server
sudo systemctl enable --now ssh-tunnel-agent