SSH & Remote Administration

Stop bouncing through jump hosts like a game of hopscotch

🧩 The Challenge

You know that feeling when you’re trying to reach a database server buried behind three different bastions, and you’re stuck manually SSHing into each one? I’ve wasted entire afternoons just trying to get a tunnel established before I can even start working.

💡 The Fix

Use the ProxyJump configuration in your SSH client. It handles the daisy-chaining for you automatically so your local machine connects directly to the final destination while using the intermediate servers as simple conduits.

Host final-server
ProxyJump user@bastion-a,user@bastion-b
HostName 10.0.5.20

⚙️ Why It Works

Setting this in your config file tells the local SSH client to build the secondary connections before initiating the final handshake. It’s way cleaner than manual port forwarding and avoids having to copy your keys onto every hop along the way.

🚀 Pro-Tip: Keep your agent forwarding disabled for the middle hops unless you absolutely need it; use the jump host directive to keep your private keys safe on your local workstation.

Linux Tips & Tricks | © ngelinux.com | 10/19/2026