You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You would need to do this on the egress side, in other words being able to specify that on the bastion itself, the command to build the egress tunnel be something like ssh -J proxyuser@proxyjump:proxyport -p port user@host, instead of ssh -p port user@host, is that correct?
If this is the case, it's not currently possible to do it, but it should be easy to implement, as long as the proxyuser@proxyjump:proxyport is fixed per-host (in a group or through personal accesses).
Correct. Maybe ingress connection does not even have to know how egress connection is done, so egress side only seems acceptable. I imagine the proxy jump being fixed per-host, yes.
Is that possible to add a server in a group using an SSH proxy jump ?
The text was updated successfully, but these errors were encountered: