Configuring additional IPv4 subnets on CentOS Print

  • 10

In most cases, your additional IPv4 subnets will be configured by our technical team, but there are certain cases, like when you opt for a server with multiple subnets in static routing, or when you are ordering IP addresses additionally to the resources provided at the time of provisioning. In these cases, we require you to configure the subnets on the server level.

In any case, if the server is managed, we'll do all these for you. If your server is unmanaged, and if you don't want to do all these by yourself, you can get in touch with our Sales for custom quote for the configuration of these from our end.

Before you proceed further with this tutorial, you have to disable the NetworkManager in CentOS 8. You can find more on how you can do it here: https://www.thegeekdiary.com/how-to-disable-networkmanager-in-centos-rhel-8/

One the NetworkManager is disabled on the server, follow these steps:

Step 1: Go to the /etc/sysconfig/network-scripts directory

Step 2: Determine which interface it is, for this example, we assume it is ifcfg-eno2

Step 3: If your main network interface is eno2, then create a ifcfg-eno2-range0 file in the /etc/sysconfig/network-scripts directory with the following information (in the below example, we use range 23.94.17.136/29)

IPADDR_START=23.94.17.137
IPADDR_END=23.94.17.142
CLONENUM_START=1
NETMASK=255.255.255.248
ARPCHECK=no

If you have multiple subnets to be configured, proceed further with Step 4.

Step 4: Repeat step #3 for all the ranges, just increase the range number by one. So after you create ifcfg-eno2-range0, create ifcfg-eno2-range1, and so on. Be sure to increase the CLONENUM_START with the number of ips that were added. So ifcfg-eno2-range1 should for example be CLONENUM_START=7

We hope that this article has helped you.


Was this answer helpful?

« Back