[GH-ISSUE #250] groupAddServer with jump #64

New issue

Open

opened 2026-05-07 00:18:19 +02:00 by BreizhHardware · 2 comments

BreizhHardware commented

2026-05-07 00:18:19 +02:00

Owner

Originally created by @mvalois on GitHub (Oct 6, 2021).
Original GitHub issue: https://github.com/ovh/the-bastion/issues/250

Is that possible to add a server in a group using an SSH proxy jump ?

Originally created by @mvalois on GitHub (Oct 6, 2021). Original GitHub issue: https://github.com/ovh/the-bastion/issues/250 Is that possible to add a server in a group using an SSH proxy jump ?

BreizhHardware added the

feature

label

2026-05-07 00:18:19 +02:00

BreizhHardware commented

2026-05-07 00:18:19 +02:00

Author

Owner

@speed47 commented on GitHub (Oct 15, 2021):

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).

@speed47 commented on GitHub (Oct 15, 2021): 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).

BreizhHardware commented

2026-05-07 00:18:20 +02:00

Author

Owner

@mvalois commented on GitHub (Oct 15, 2021):

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.

@mvalois commented on GitHub (Oct 15, 2021): 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.

BreizhHardware referenced this issue

2026-05-07 00:19:48 +02:00

[PR #64] [MERGED] fix: Enable perl-tidy.sh test #207