TransIT AI
Sign up

Sessions & terminal

Connect through a jump host

When the device you want isn’t reachable directly — it lives behind a bastion, a management jump box, or a work laptop — point it at a jump host and Transit tunnels through for you. The full story, including how the tunnel keeps the bastion out of your session, is on the Jump hosts page; this is the quick setup.

Requires Transit 6.5.0 or later. Both the target device and the jump host must already be in your inventory.

Set the jump host

  1. Right-click the target device → Edit (or double-click it), and open the Connection section.
  2. Find Jump host and open the picker. It’s searchable — type a device name or an IP to filter a large inventory.
  3. Choose the device to tunnel through. The chain preview shows the path (You → jump → this device).
  4. Save.

That’s it — the device now connects through that host every time. To undo it, open the picker and choose Direct connection, or click the reset (×) button beside it.

Connect

Connect the device the way you always do — right-click Connect, double-click, or focus-and-Enter. On the first connection you’ll be asked to trust the jump host’s key, then the target’s key: two prompts, each naming its host. After that, connecting is one step as usual.

If the jump host refuses to open the tunnel — most often its sshd has AllowTcpForwarding no — the error says so and names the jump host, so you know which end to fix.

Set one jump host for many devices

Select several devices in the sidebar (Shift-click a range, or Cmd/Ctrl-click to pick individually), right-click → Edit N devices, set Jump host, and apply. Every selected device gets the same bastion in one step.

Confirm the hop actually happened

Ask the device itself. On a jumped Cisco device, show users lists your SSH session with a source address that’s the jump host’s IP, not your workstation’s — proof the connection traversed the bastion. Most platforms have an equivalent (show system users, who, and so on).

Chains

A jump host can have its own jump host, up to four hops deep — useful when a lab or customer network nests bastions. Set each device’s jump host and Transit walks the chain in order, trusting each hop as it goes.