Connect a remote desktop to other products

Last update: July 28 2026Open in Markdown

You can connect your remote desktops (DaaS) with other products over a private network. This connection allows you to interact completely remotely with resources in the Selectel infrastructure, such as a cloud server, database, and data center in VMware-based cloud, as well as connect to a Direct Connect or Global Connect channel. In this case, traffic between the remote desktop and other resources will remain within the Selectel private network.

The network is organized via a global router.

You cannot configure internet access for a remote desktop through another product (announce a default route to 0.0.0.0/0 through the global router).

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

2. Connect the network and subnet to the remote desktop to the global router.

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

4. On the server in the other product, specify static routes to the remote 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. Each account has a limit of five global routers.
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. Submit a ticket to connect the remote desktop to the global router. In the ticket, specify the ID of the global router that you created in step 1. It can be viewed in the control panel under Network Services → Selectel Global Router → router page → field under the router name.

2. We will connect a private subnet of size /26 from the 172.16.0.0/12 block, where your remote 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, go to step 3;
   • if you are configuring connectivity with a VMware-based cloud, proceed to the Methods for connecting public cloud to a global router instructions, select the appropriate method, and perform the corresponding settings on the public cloud side, starting with creating a subnet for connecting 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:

• a /26 block from the 172.16.0.0/12 subnet where your remote desktops are located;
• the 10.49.32.0/24 service subnet.

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, from 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 hardware service.

6. Select the location of 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, because 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 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 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 in Managed Kubernetes internal addressing, and their use may lead to conflicts in the global router network.

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, from the top menu, click Products → Global Router → router page → Network map.

15. If you specified a Q-in-Q tag in step 8, enable Q-in-Q on the switch port and configure the network interface of the private network specified in step 10. Learn more in the Configure Q-in-Q section of the Q-in-Q instructions.

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, in the top menu, click Products and select Global Router.

2. Open the router page → the 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 the location of 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 private address range according to RFC 1918: 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16;
   • have a size of at least /29, because 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 added 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 added 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 participate in Managed Kubernetes internal addressing, and using them may lead to 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, in the top menu, click Products → Global Router → router page → Network map.

Connect an existing network

1. Make sure the network has not yet been added to any of the account's global routers. In the control panel, in the top menu, click Products → Cloud Servers → Network → the Private networks tab → check that the network card does not have the tag Global router.

2. Verify that the subnet meets the following conditions:

   • belongs to the private address range according to RFC 1918: 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16;
   • has a size of at least /29, because 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 added 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 added 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 participate in Managed Kubernetes internal addressing, and using them may lead to conflicts in the global router network.

3. In the control panel, in the top menu, click Products and select Cloud Servers.

4. Go to Network → the Private networks tab.

5. In the menu of the network, 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 stating that the network has been connected. After this, in the control panel:

   • the network will appear in the section Selectel Global Router on the page of the router to which you connected it;
   • in the section Cloud Servers → Network → on the Private networks tab, 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> — subnet to which the route is needed, specifying the mask, for example, 172.16.10.10/26;
   • <gateway> — gateway for the current server subnet 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> — subnet to which the route is needed, for example, 172.16.10.10;
   • <mask> — mask of the subnet to which the route is needed, for example, 255.255.255.192;
   • <gateway> — gateway for the current server subnet 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> — subnet to which the route is needed, specifying the mask, for example, 172.16.10.10/26;
   • <gateway> — gateway for the current server subnet specified on the global router;
   • <eth_name> — 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> — subnet to which the route is needed, for example, 172.16.10.10;
   • <mask> — mask of the subnet to which the route is needed, for example, 255.255.255.192;
   • <gateway> — gateway for the current server subnet specified on the global router;
   • <x> — parameter that defines the priority of the specified gateway, 1 is the highest priority.

Cloud platform

To specify static routes for a cloud server, Managed Databases cluster, or Managed Kubernetes cluster, configure static routes in 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.