2

enter image description here

I am aware that it is possible to forward SSH from server A to server B by creating a tunnel.

What I am asking for is rather the red alternative on the schema above. Can this scenario be implemented:

  1. SSH to server A
  2. Server A tells client to go to server B instead
  3. Server B communicates directly with client over SSH

So basically a sort of proxy that after introducing the client-server to each other, he gets out of the communication.

I imagine using a firewall redirection doesn't offer much customization.

What I seek ultimately is a way to make access through SSH to git mirrors transparent for client depending on geolocation.

Advanced scenario scenario

  1. Client Pulling from server A and is closer to server B is redirected to B
  2. When pushing, client remains on server A
Jeff Schaller
  • 66,199
  • 35
  • 114
  • 250
Ezwig
  • 490
  • 1
  • 4
  • 14

2 Answers2

1

You can think of this kind of wrapping:

  • servers, or just the main server holds a git transfer initialisation script
  • in the clients, define Git aliases that will get the target server by executing that script on the main server (or any of the servers)

If you only need to redirect pull, then you need one alias. But probably you'll also want to redirect fetch (if not more commands, I'm not that good with Git).

  • I thought about that. The constraint is that client should be agnostic to the change. I was hoping for soething similar to http redirect. Like apache mod_rewrite for http but for ssh. – Ezwig Jun 21 '18 at 13:22
1

Unfortunately there is no flag to turn on in SSH to do this. You'd have to code something custom for GIT. (i.e. if serverA has lower ping time than server B use A or vice vera)

Joe M
  • 866
  • 4
  • 6
  • The target, is to achieve a setup that is transparent for clients. If i will be doing a customization, i would want it to be on server side – Ezwig Jun 21 '18 at 13:27