Port Forwarding

Port forwarding

English · Русский

The Tunnels section holds saved forwards, independent of whether their host has a session open.

Types

Type	OpenSSH equivalent	What it does
Local forward	-L	a port on this machine reaches a destination through the host
Remote forward	-R	a port on the host reaches a destination through this machine
Dynamic SOCKS	-D	a SOCKS5 proxy on this machine; each client picks its own destination

A tunnel is defined by a name, the host it goes via, a bind address, a port, and (except for SOCKS) a destination.

The dashboard

Each row shows name, listen address, target, host, live throughput and status — active, connecting, failed, stopped. Local forwards to a web service have an Open in browser action.

Edits apply after the tunnel is restarted; removing an active tunnel disconnects it first and says so.

Raising tunnels

Tunnels come up automatically once the vault is unlocked and their host is reachable — you do not have to open a session first. A tunnel whose host is down shows failed and retries when the host comes back.

Discovering ports

Scan ports asks a host which TCP ports it is listening on and lists them. Any of them can be forwarded in one tap; ports already forwarded are marked. Connection types with no command channel (Telnet, serial, VNC/RDP) cannot be scanned.

Sharing the pattern

Tunnels are vault records, so they sync across your devices and can go to the trash and be restored like anything else.