Archived

This forum has been archived. Please start a new discussion on GitHub.

Can Glacier2 be chained?

Rong
Rong
in Help Center
Glacier2 seems appropriate for that clients reside in public network and servers reside in private network.

But our situation is, we have two IDCs in different city, but now we don't have dedicated line between them. If clients reside in IDC A, and servers reside in IDC B. Both IDCs have a machine which owns public IP and privte IP.

Client --> Interface Machine(IDC A) ----public network----> Interface Machine(IDC B) --> Server, is the only feasible physical channel.

So I wonder if Glacier2 can be chained, transfer requests and response transparently.

Thanks.

Comments

  • Rong
    Rong
    maybe I need to make this more clear.

    How to make such configuration?:

    A client send request to a Glacier2, this Glacier2 doesn't send request to server directly, but send to another Glacier2 instead, and the second Glacier2 can reach the real server.
  • benoit
    benoit Rennes, France
    Hi Rong,

    Sorry, Glacier2 doesn't support chaining. There can only be one Glacier2 router between a client and server. The Glacier2 router is typically deployed in the private network of the server and can listen for incoming connections on the public network (see the Ice manual for typical deployment scenarios).

    In your case, the clients in IDC A would need to be able to establish outgoing connections to the Glacier2 router deployed in IDC B. Of course, if your clients don't have any acccess to the public network, this doesn't work.

    If you have a commercial interest in such a feature, we could look into implementing it. If that's the case, please contact us at info@zeroc.com!

    Benoit.

Categories