Domain route via VPN

Overview

See Domain route via VPN

Configuring Domains to Route via VPN

To configure the processes to route through the VPN, use the ConfigureRouteViaVpnDomains or ConfigureRouteViaVpnDomainsAsync method of the SDK. Here's an example:

var sdk = new SDK();
var routeViaVpnDomainsRequest = new RouteViaVpnDomainsRequest
{
    UpdateRouteViaVpnDomains = new UpdateRouteViaVpnDomainsRequest()
    {
        Domains = new List<string> { "foobar.com" },
    },
};

var routeViaVpnDomainsResponse = await sdk.ConfigureRouteViaVpnDomainsAsync(routeViaVpnDomainsRequest).ConfigureAwait(false);
Console.WriteLine(routeViaVpnDomainsResponse.UpdateRouteViaVpnDomains.Result);

In this example, we create a new RouteViaVpnDomainsRequest and specify the list of processes to route via VPN in the Domains property. Then we pass this request to the ConfigureRouteViaVpnDommainsAsync method.

Starting the VPN with Processes Route via VPN Enabled

After configuring the processes, you can start the VPN with the "Domain route via VPN" feature enabled:

var startVpnRequest = new StartVpnRequest()
{
    AccessToken = loginResponse.AccessToken,
    Credentials = getCredentialsResponse.Credentials,
    EnableRouteViaVpn = true,
    
    // Should be disabled for proper Route via VPN work, see limitations
    EnableKillSwitch = false,
    BlockLocalNetworks = false,
    EnablePreventIPLeak = false,
};

sdk.StartVpn(startVpnRequest);
// Message: "Ok"
// Result: Ok

Limitations

Please note the following limitations of the "Domain route via VPN" feature:

• It cannot be enabled or disabled while the VPN tunnel is active. You must configure it before starting the VPN.

• Defense features (Killswitch, Prevent IP Leaks and Block LocalNetwork) should be disabled with enabling the Route via VPN feature (pass corresponding parameters in the StartVpnRequest with enabling the Route via VPN).

More Information

See Common Issues