Support for proxying through bastion hosts (with the option of agent forwarding, even though it can be exploited) is critical for professionals.
In terms of ssh config, bastionhost.example.com is set up elsewhere, then we need the option to do:
ssh -o User=myuser -W %h:%p bastionhost.example.com
+1. There's another request for this as well.
An indicator on each host, green for good, yellow for high RTT, and red for no connectivity, would be very useful. Maybe different shapes for visually impaired people.
Or at very least a way to increase it to a significantly larger value on a per host or group basis.
Could you guys please provide the exact examples of the ProxyCommands that you use in your setups?
This will help to understand to the variety of cases and what to focus on first.
@william: totally agree with your comment.
+1: see my comment on the VPN request. I wrote that before I saw this request.
This is a major convenience function when there are many hosts. I have dozens, and adding them one by one is torturous.
Also, many larger environments use a jump host (bastion host) through which you need to tunnel over ssh (ssh -D) and forward (ssh -A) keys to get to internal systems. It is very inconvenient to have to log on to the jump host and then manually ssh to the internal one.
It's not exactly a VPN, but I really need to ability to tunnel through a proxy host.