Tunnels and jump hosts
Tunnels forward network ports through an SSH connection. Open one from Tunnels in a terminal, and save it to start it later from the Tunnels page or the tray or menu bar icon.
Tunnel types
| Type | Same as | What it does |
|---|---|---|
| Local | ssh -L | A port on your computer (127.0.0.1) reaches a host and port seen from the server, for example a database that listens only on the server. |
| Remote | ssh -R | A port on the server reaches a host and port seen from your computer. The server must allow it (AllowTcpForwarding in sshd_config); port 0 lets the server pick one. |
| SOCKS (dynamic) | ssh -D | A SOCKS5 proxy on 127.0.0.1 of your computer; programs that use it send their traffic through the server. |
Saved tunnels
- Check “Save this tunnel” when you open it. Saved tunnels need fixed ports: a local port for local and SOCKS tunnels, a server port for remote ones.
- Two saved tunnels cannot use the same local port.
- Saved tunnels run in the background while the app is open; turn each on or off from the Tunnels page or the tray (Windows) or menu bar (macOS). The tray tooltip shows how many are open.
- Saved tunnels are part of backups and sync.
Jump hosts
To reach a server that is only reachable through another one, edit the server and choose a saved host as its jump host. The app connects to the jump host first and opens the connection to the target through it. A host is never its own jump host and loops are refused. Mosh does not work through a jump host; use SSH for such a server.
- Servers (hosts), groups and quick connect: Add and organise SSH servers in the desktop app: groups, import from ~/.ssh/config, quick connect, startup commands, environment variables and agent forwarding.
- Telnet, serial ports and Mosh: Connect to old devices over Telnet, to network equipment and boards over a serial port, and keep a terminal alive on unstable networks with Mosh.