Skip to main content
Link products and services through a global router
Last update:

Link products and services through a global router

General instructions for setting up a global router network for all Selectel products. For configuration examples for individual products (dedicated servers, cloud databases, Managed Kubernetes), see Link products and services via global router.

For your information

Some dedicated server configurations Chipcore Line cannot be added to the global router network because they do not have a port to connect to the private network. The availability of a private network port can be checked in control panel on the server page under the Ports tab.

  1. Create global router.
  2. Connect-networks-and-subnets-to-global-router to each VLAN and cloud platform project whose servers you want to merge. For VMware-based Cloud, you can only add networks and subnets through technical support.
  3. Assign IP addresses from created subnets to servers.
  4. Optional: write-routes-on-servers.
  5. Optional: configure-routing-on-global-router.

1. Create a global router

  1. In Control Panel, go to Network ServicesSelectel Global Router.
  2. Click Create Router. Each account has a limit of five global routers.
  3. Enter the name of the router.
  4. Press Create.
  5. If the router was created with status ERROR or hung in one of the statuses, create a ticket.

2. Connect networks and subnets to a global router

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 Control Panel, go to Network ServicesSelectel Global Router.

  2. Open the router page → Networks tab.

  3. Click Create Network.

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

  5. Select the Dedicated Servers service.

  6. Select pool.

  7. Select VLAN. If you want to network to an internal segment (Q-in-Q), specify its tag, a number between 2 and 4094. If there is already a network upstream of the VLAN, be sure to specify the Q-in-Q segment of that VLAN.

  8. Enter the subnet name — this will only be used in the control panel.

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

    • belong to the RFC 1918 private address range of 10.0.0.0.0/8, 172.16.0.0.0/12, or 192.168.0.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: The IP addresses of each subnet on the router must not overlap with the IP addresses of other subnets on the router;
    • if Managed Kubernetes nodes will be included in the global router network, the subnet must not overlap with the 10.250.0.0.0/16, 10.10.0.0.0/16, and 10.96.0.0.0/12 ranges. These subnets participate in the internal addressing of Managed Kubernetes, their use can cause conflicts in the global router network.
  10. If you specified the Q-in-Q tag, make sure to configure Q-in-Q. When configuring, use the subnet you specified in step 9.

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

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

  13. Click Create Network.

  14. Optional: check the network topology on the global router. In Control Panel, go to Network ServicesSelectel Global Router. Open the page of the desired router and click Network Map.

3. Assign IP addresses to the servers

On each server that is included in the global router network, configure a local port to work with the subnet created on the router. On the port, assign an IP address from the private subnet that you connected to the global router for the appropriate VLAN or project.

  1. Connect to the server via SSH or via KVM-console.

  2. Open the netplan utility configuration file with the vi text editor:

    vi /etc/netplan/01-netcfg.yaml
  3. Add or change values for the network interface settings of the private network:

        <eth_name>:
    addresses: [<ip_address>/<mask>]

    Specify:

    • <eth_name> is the name of the network interface of the private network;
    • <ip_address>/<mask> — the private IP address of the server with a subnet mask, for example, 192.168.0.2/29.
  4. Press the ESC key.

  5. Exit the vi text editor with the changes saved:

    :wq
  6. Apply the configuration:

    netplan apply
  7. Optional: reboot the server.

4. write routes on the devices

If you have created a new server and added it to an existing global router network, you do not need to specify routes. In this case, the server will be immediately available to other devices on the network.

If you are adding an existing server to the global router network, you must #write-static-routes to all subnets with which you want connectivity.

Example of static route organization

You need to configure private communication between two dedicated servers in the SPB-1 pool and a cloud server in the ru-2 pool. To do this, you need:

  1. Create a global router with two private subnets — 192.168.0.0.0/29 to the VLAN that contains the dedicated servers in pool SPB-1, and 172.16.0.0.0/29 to the cloud platform project in pool ru-2.

  2. Assign addresses from subnets to servers.

  3. write routes:

    • on each server in the SPB-1 pool to the 172.16.0.0.0/29 subnet via the 192.168.0.1 gateway;
    • on the server in pool ru-2 — to subnet 192.168.0.0.0/29 through gateway 172.16.0.1.

Example of static route organization
Example of static route organization

write static routes

<Tabs>
<TabItem value="Ubuntu" label="Ubuntu" default>

1. [Connect to server](/servers-and-infrastructure/dedicated/manage/connect-to-server.mdx).
2. Open the network configuration file:

```
vi /etc/netplan/01-netcfg.yaml
```

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

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

Specify:
* ` `<ip_address>/<mask>` - the subnet to which the route is needed, specifying the mask, e.g., `192.168.0.0.0/29`;
* `<gateway>` - the gateway for the current server subnet, which is specified on the global router.

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

`` ``
routes:
- to: 192.168.0.0.0/29
via: 172.16.0.1
- to: 192.168.1.0.0/29
via: 172.16.0.1
```

5. Save the file.
6. Check the settings:

```
sudo netplan try
```

7. Apply the changes:

`` ``
netplan apply
`` ``

</TabItem>

<TabItem value="Debian" label="Debian">

1. [Connect to server](/servers-and-infrastructure/dedicated/manage/connect-to-server.mdx).
2. Open the network configuration file:

```
vi /etc/network/interfaces
```

3. At the end of the corresponding network interface data block, add the desired 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 which the route is needed, e.g., `192.168.0.0`;
* `<mask>` - the subnet mask to which the route is needed, e.g., `255.255.255.0`;
* `<gateway>` - the gateway for the current server's subnet, which is specified on the global router.

4. If you need to prescribe multiple routes, add them sequentially in the same block.
5. Save the file.
6. Restart the network:

```
sudo /etc/init.d/networking restart
```

</TabItem>
<TabItem value="CentOS" label="CentOS">

1. [Connect to server](/servers-and-infrastructure/dedicated/manage/connect-to-server.mdx).
2. Create and complete 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 which the route is needed, specifying the mask, for example, `192.168.1.0.0/29`;
* `<gateway>` - the gateway for the current server's subnet, which is specified on the global router;
* `<eth_name>` - the name of the corresponding LAN interface.

If you need to add several routes, specify them in one command. Specify each route on a new line, for example:

```
echo "192.168.0.0.0/29 via 172.16.0.1
192.168.1.0.0/29 via 172.16.0.1" >> /etc/sysconfig/network-scripts/route-eno2
```

3. Restart the network:

```
systemctl restart network
```

</TabItem>

<TabItem value="windows" label="Windows">

1. [Connect to the server via RDP](/servers-and-infrastructure/dedicated/manage/connect-to-server.mdx#connect-via-rdp) or via [KVM-console](/servers-and-infrastructure/dedicated/manage/connect-to-server.mdx#connect-via-kvm-console).
2. Add the required routes one at a time:

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

Specify:
* ` `<ip_address>` - the subnet to which the route is needed, for example, `192.168.0.0`;
* `<mask>` - the subnet mask to which the route is needed, for example, `255.255.255.0`;
* `<gateway>` - the gateway for the current server subnet, which is specified on the global router;
* `<x>` - the parameter that determines the priority of the specified gateway, 1 being the highest priority.

</TabItem>
</Tabs>

5. Configure routing on a global router

You need to write static routes or configure dynamic BGP routing on the global router if you:

  • organize Internet access on the global router network through one of the connected devices;
  • or you plan to use a network larger than /29 and your server as a router.
  1. In Control Panel, go to Network ServicesSelectel Global Router.
  2. Open the router page → Static Routes tab.
  3. Press Create Route.
  4. Enter a route name — any name, it will only appear in the control panel.
  5. Enter the CIDR of the destination subnet — this is the private subnet to which you want to direct traffic. The destination subnet must not overlap with subnets on the global router. To direct Internet traffic to one of the devices on the global router network, specify 0.0.0.0.0/0/0.
  6. Enter the IP address Next hop — the IP address of the server through which traffic will be routed to the destination subnet. The IP address must belong to one of the subnets on the global router.
  7. Press Create.