Configure static routes on dedicated servers

Static routing is a type of routing in which routes are specified explicitly when configuring a network interface on a server or router.

To configure static routing, write static routes on the server.

Examples of problems that can be solved using static routing:

• link dedicated servers and cloud server over a private network.

Write static routes on the server

Ubuntu

1. Connect to the server.

2. Open the network interfaces configuration file with the vi text editor:

   vi /etc/netplan/01-netcfg.yaml

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

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

   Specify:

   • <ip_address> - subnet to which the route is needed;
   • <mask> - mask of the subnet to which you want to route;
   • <gateway> - gateway for the subnet of the current server, such as the gateway listed on the global router. The gateway address must be on the same subnet as the server.

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

   routes:
   - to:  192.168.0.0/28
     via: 192.168.0.1
   - to:  192.168.1.0/28
     via: 192.168.0.1

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

   :wq

6. Check the routing configuration:

   sudo netplan try

7. Apply the changes:

   netplan apply

Debian

1. Connect to the server.

2. Open the network interfaces configuration file with the vi text editor:

   vi /etc/network/interfaces.d/50-cloud-init

3. Add the desired route at the end of the parameter block for the corresponding network interface:

   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 you want to route, e.g. 192.168.0.0;
   • <mask> - mask of the subnet to which the route is to be routed, e.g. 255.255.255.0;
   • <gateway> - the gateway for the subnet of the current server, such as the gateway listed on the global router. The gateway address must be on the same subnet as the server

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

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

   :wq

6. Restart the network:

   sudo /etc/init.d/networking restart

CentOS

1. Connect to the server.

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> - subnet to which the route is needed;
   • <mask> - mask of the subnet to which you want to route;
   • <gateway> - the gateway for the subnet of the current server, such as the gateway listed on the global router. The gateway address must be on the same subnet as the server;
   • <eth_name> - the name of the corresponding LAN interface.

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

   echo "192.168.0.0/28 via 172.16.0.1
   192.168.1.0/28 via 172.16.0.1" >> /etc/sysconfig/network-scripts/route-eno2

4. Restart the network:

   systemctl restart network

Windows

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

2. Add the required routes one at a time:

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

   Specify:

   • <ip_address> - the subnet to which you want to route, e.g. 192.168.0.0;
   • <mask> - mask of the subnet to which the route is to be routed, e.g. 255.255.255.0;
   • <gateway> - the gateway for the subnet of the current server, such as the gateway listed on the global router. The gateway address must be on the same subnet as the server;
   • <x> - parameter that determines the priority of the specified gateway, 1 being the highest priority.

Example of organizing static routes to connect dedicated servers and a cloud server over a private network

Purpose of customization

Connect the two dedicated servers in the SPB-2 pool and the cloud server in the ru-2 pool with a private network using a global router and configure routing in the network so that the devices see each other.

What you need to customize

In the example, we used two dedicated servers in the SPB-2 pool with access to the private network and a cloud server in the ru-2 pool for configuration.

Customization result

Private connectivity will be configured between the two dedicated servers in the SPB-2 pool and the cloud server in the ru-2 pool.

Customization steps

1. Create a global router.

2. Connect the private subnets to the global router:

   • 192.168.0.0/28 to the VLAN that contains the dedicated servers in the SPB-2 pool;
   • 172.16.0.0/28 for the cloud platform project in the ru-2 pool.

3. Assign IP addresses from the private subnets that you connected to the global router to the dedicated servers and the cloud server. For more information, see Assign IP addresses to servers.

4. Spell out the routes:

   • on each dedicated server in the SPB-2 pool to subnet 172.16.0.0/28 via gateway 192.168.0.1;
   • on the cloud server in pool ru-2 - to subnet 192.168.0.0/28 via gateway 172.16.0.1.