Connect a remote desktop to other products

Last update: June 10 2026

You can connect your Desktop as a Service (DaaS) to other products via a private network. This connection allows you to interact fully remotely with resources in the Selectel infrastructure, such as a cloud server, database, or a VMware-based cloud data center, and to connect to a Direct Connect or Global Connect line. In doing so, traffic between your desktop and other resources will remain within the Selectel private network.

The network is set up via a global router.

You cannot configure internet access for a virtual desktop through another product (do not announce a default route to 0.0.0.0/0 via a global router).

1. If you do not have a global router yet, create a global router.

2. Connect the network and subnet for the virtual desktop to the global router.

3. Connect the network and subnet for the server in another product that you want to link with the virtual desktop to the global router.

4. On the server in the other product, add static routes to the virtual desktop subnet.

1. Create a global router

1. In the Control panel, in the top menu, click Products and select Global Router.
2. Click Create router. A limit of five global routers is set for each account.
3. Enter the router name.
4. Click Create.
5. If the router was created with the status ERROR or is stuck in one of the statuses, create a ticket.

2. Connect the network and subnet for the virtual desktop to the router

1. Create a ticket to connect a virtual desktop to a global router. In the ticket, specify the ID of the global router that you created in step 1. You can find it in the control panel under Network Services → Selectel Global Router → router page → field under the router name.

2. We will connect a private subnet with a size of /26 from the 172.16.0.0/12 block, where your virtual desktops are located, to the global router. This subnet will not be displayed on the global router page in the control panel.

3. Wait for confirmation that connectivity has been configured.

4. Depending on which product you are connecting your virtual desktops to:

   • if you are configuring connectivity with a cloud server, dedicated server, or Managed Kubernetes cluster, proceed to step 3;
   • if you are configuring connectivity with a VMware-based cloud, follow the Ways to Connect a Public Cloud to a Global Router guide, select the appropriate method, and perform the necessary settings on the public cloud side, starting by creating a subnet to connect the public cloud to the global router.

3. Connect the network and subnet for the server in another product to the router

The subnet in the other product must not overlap with the DaaS service networks:

• the /26 block from the 172.16.0.0/12 subnet that contains your virtual desktops;
• the service subnet 10.49.32.0/24.

Dedicated server

Use for a dedicated or hosted server.

You can connect a new network to the router or an existing network if it is not already connected to any of the account's global routers.

1. In the control panel, on the top menu, click Products and select Global Router.

2. Open the router page → Networks tab.

3. Click Create network.

4. Enter a network name. It will only be used in the control panel.

5. Select the Servers and Equipment service.

6. Select a location for the network.

7. Select or enter a VLAN.

8. If you want to create a network to an internal segment (Q-in-Q), specify its tag — a number from 2 to 4094. If a network already exists for the VLAN, you must specify the Q-in-Q segment of this VLAN.

9. Enter a subnet name. It will only be used in the control panel.

10. Enter the CIDR — the IP address and mask of the private subnet. You can enter a new subnet or an existing private server subnet if it has not yet been added to any of the global routers in the account. The subnet must meet the following conditions:

    • belong to the RFC 1918 private address range: 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16;
    • have a size of at least /29, as three addresses will be occupied by Selectel network equipment;
    • do not overlap with other subnets added to this router — there must be no identical IP addresses within subnets on the same router;
    • if a Managed Kubernetes cluster on cloud servers is to be connected to the global router network, the subnet must not overlap with the ranges 10.10.0.0/16, 10.96.0.0/12, 10.250.0.0/16 and 10.251.0.0/24. If a cluster on dedicated servers is to be connected to the network — with the ranges 10.10.0.0/16, 10.222.0.0/16, 10.250.0.0/16, 10.251.0.0/24 and 172.250.0.0/14. These subnets are used for internal Managed Kubernetes addressing; using them may lead to network conflicts in the global router.

11. Enter the gateway IP or leave the first address from the subnet, which is assigned by default. Do not assign this address to your devices to avoid network disruption.

12. Enter the service IPs or leave the last addresses from the subnet, which are assigned by default. Do not assign these addresses to your devices to avoid network disruption.

13. Click Create network.

14. Optional: check the network topology on the global router. In the control panel, on the top menu, click Products → Global Router → router page → Network map.

15. Если on шаге 8 вы указали тег Q-in-Q, нужно включить технологию Q-in-Q on порту коммутатора and настроить сетевой интерфейс приватной сети, которую вы указали on шаге 10.Подробнее in подразделе Настроить Q-in-Q инструкции Q-in-Q

Cloud platform

Use for a cloud server, Managed Kubernetes cluster nodes, or Managed Database clusters.

You can connect a new or existing network to the router if it is not already connected to any of the account's global routers.

Connect a new network

1. In the Control panel, on the top menu, click Products and select Global Router.

2. Open the router page → Networks tab.

3. Click Create network.

4. Enter a network name. It will only be used in the control panel.

5. Select the Cloud Platform service.

6. Select a location for the network.

7. Select a project.

8. Enter a subnet name. It will only be used in the control panel.

9. Enter the CIDR — IP address and subnet mask. The subnet must meet the following conditions:

   • belong to the RFC 1918 private address range: 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16;
   • have a size of at least /29, as three addresses will be occupied by Selectel network equipment;
   • it does not overlap with other subnets added to this router — there must be no identical IP addresses within the subnets of one router;
   • if a Managed Kubernetes cluster on cloud servers is to be connected to the global router network, the subnet must not overlap with the 10.10.0.0/16, 10.96.0.0/12, 10.250.0.0/16 and 10.251.0.0/24. If a cluster on dedicated servers is connected to the network, it must not overlap with the 10.10.0.0/16, 10.222.0.0/16, 10.250.0.0/16, 10.251.0.0/24 and 172.250.0.0/14. These subnets are used for Managed Kubernetes internal addressing, and their use may cause conflicts in the global router network.

10. Enter the gateway IP or leave the first address from the subnet, which is assigned by default. Do not assign this address to your devices to avoid disrupting network operation.

11. Enter the service IPs or leave the last addresses from the subnet, which are assigned by default. Do not assign these addresses to your devices to avoid disrupting network operation.

12. Click Create network.

13. Optional: check the network topology on the global router. In the Control panel, on the top menu, click Products → Global Router → router page → Network Map.

Connect an existing network

1. Ensure the network is not already added to any global router in your account. In the Control panel, on the top menu, click Products → Cloud Servers → Network → tab Private networks → check that the network card does not have the tag Global Router.

2. Verify that the subnet meets the following conditions:

   • belongs to the RFC 1918 private address range: 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16;
   • is at least /29, as three addresses will be occupied by Selectel network equipment;
   • it does not overlap with other subnets added to this router: the IP addresses of each subnet on the router must not match the IP addresses of other subnets on it;
   • if a Managed Kubernetes cluster on cloud servers is to be connected to the global router network, the subnet must not overlap with the 10.10.0.0/16, 10.96.0.0/12, 10.250.0.0/16 and 10.251.0.0/24. If a cluster on dedicated servers is connected to the network, it must not overlap with the 10.10.0.0/16, 10.222.0.0/16, 10.250.0.0/16, 10.251.0.0/24 and 172.250.0.0/14. These subnets are used for Managed Kubernetes internal addressing, and their use may cause conflicts in the global router network.

3. In the Control panel, on the top menu, click Products and select Cloud Servers.

4. Go to Network → tab Private networks.

5. From the network menu, select Connect to Global Router.

6. Select a global router.

7. For each subnet in the network, enter the IP address to be assigned to the router or leave the first available address from the subnet, which is assigned by default. Do not assign this address to your devices to avoid disrupting network operation. The last two available subnet addresses will be reserved as service addresses.

8. Click Connect. Do not close the window until a message appears confirming the network has been connected. After that, in the control panel:

   • the network will appear in the section Selectel Global Router on the router page to which you connected it;
   • in the section Cloud Servers → Network → on the tab Private networks, the network will have the tag Global Router.

4. Add a static route to the virtual desktop subnet

On the device in the other product, add static routes to the virtual desktop subnet:

• as the destination subnet, specify the CIDR of the virtual desktop subnet;
• as the gateway, specify an address from the subnet to which the relevant server has been added and which is used as the global router gateway.

Dedicated server

Use for a dedicated or hosted server.

Ubuntu

1. Connect to the server.

2. Open the network configuration file:

   vi /etc/netplan/01-netcfg.yaml

3. At the end of the block containing the data for the desired network interface, add the route:

   routes:
     - to: <ip_address>/<mask>
       via: <gateway>

   Specify:

   • <ip_address>/<mask> — the subnet to reach, including the mask, for example, 172.16.10.10/26;
   • <gateway> — the gateway for the current server's subnet, which is specified on the global router.

4. If you need to add multiple routes, add them sequentially in the same block, for example:

   routes:
   - to: 172.16.10.10/26
       via: 192.168.0.1
   - to: 192.168.100.0/28
       via: 192.168.0.1

5. Save the file.

6. Check the settings:

   sudo netplan try

7. Apply the changes:

   netplan apply

Debian

1. Connect to the server.

2. Open the network configuration file:

   vi  /etc/network/interfaces

3. At the end of the block containing data for the corresponding network interface, add the required route:

   up route add -net <ip_address> netmask <mask> gw <gateway>
   down route del -net <ip_address> netmask <mask> gw <gateway>

   Specify:

   • <ip_address> — the subnet to reach, for example, 172.16.10.10;
   • <mask> — the subnet mask to reach, for example, 255.255.255.192;
   • <gateway> — the gateway for the current server's subnet, which is specified on the global router.

4. If you need to add multiple routes, add them sequentially in the same block.

5. Save the file.

6. Restart the network:

   sudo /etc/init.d/networking restart

CentOS

1. Connect to the server.

2. Create and fill in a file to configure static routes:

   echo "<ip_address>/<mask> via <gateway>" >> /etc/sysconfig/network-scripts/route-<eth_name>

   Specify:

   • <ip_address>/<mask> — the subnet to reach, including the mask, for example, 172.16.10.10/26;
   • <gateway> — the gateway for the current server's subnet, which is specified on the global router;
   • <eth_name> — the name of the corresponding local network interface.

   If you need to add multiple routes, specify them in a single command. Add each route on a new line, for example:

   echo "172.16.10.10/26 via 192.168.0.1
   192.168.100.0/28 via 192.168.0.1" >> /etc/sysconfig/network-scripts/route-eno2

3. Restart the network:

   systemctl restart network

Windows

1. Connect to the server via RDP or via the KVM console.

2. Add the required routes one by one:

   route -p ADD <ip_address> MASK <mask> <gateway> METRIC <x>

   Specify:

   • <ip_address> — the subnet to reach, for example, 172.16.10.10;
   • <mask> — the subnet mask to reach, for example, 255.255.255.192;
   • <gateway> — the gateway for the current server's subnet, which is specified on the global router;
   • <x> — a parameter determining the gateway priority, 1 being the highest priority.

Cloud platform

To add static routes for a cloud server, Managed Database cluster, or Managed Kubernetes cluster, you must configure static routes on the private subnet where the server or cluster is located.

In the subnet, you must configure routes to all other global router subnets with which traffic will be exchanged.