Clarification on Access Key and Token Management in VpnHood

[trudyhood]

It depends on your policy.

Distributing Servers Between Clients

If you want to distribute servers among clients so that one client will never know about the other servers, you will need to use multiple tokens. This helps in hiding other server IPs from a single token. Combining different endpoints into a single token doesn't make much sense in this context.

Load Balancing and Failover Strategy

If your goal is to load balance servers and ensure redundancy (e.g., using another IP if one is blocked), you need to add servers to a single farm. VpnHood will perform the load balancing. There are two attributes on the access server:

• Public: Users will be redirected to this endpoint for load balancing as long as they can connect to at least one PublicInToken endpoint.

• PublicInToken: This attribute will add that access point into the token and manage failover at the client side.

The process works as follows: The client connects to a PublicInToken endpoint and may be redirected to a Public endpoint for load balancing if required. If you need the client to try all endpoints in case they cannot access some, make all public access points as PublicInToken.

Feel free to ask if you have any confusion or need further clarification.