{"id":2663,"date":"2015-11-12T22:58:23","date_gmt":"2015-11-12T22:58:23","guid":{"rendered":"https:\/\/unihost.com\/help\/?p=2663"},"modified":"2024-12-13T13:59:35","modified_gmt":"2024-12-13T10:59:35","slug":"network-ip-aliasing","status":"publish","type":"post","link":"https:\/\/unihost.com\/help\/network-ip-aliasing\/","title":{"rendered":"Configuring IP aliasing"},"content":{"rendered":"

IP<\/span> aliasing is a special network configuration for your dedicated servers you to associate multiple IP<\/span>\u00a0addresses with a single network\u00a0<\/span>interface.<\/span><\/p>\n

The following sections contain the configurations for the most commonly used distributions\/operating\u00a0<\/span>systems.<\/span><\/p>\n

Concerning current distributions, please note that the proper procedure to configure your network interface may be subject to change. We recommend to consult the manuals and knowledge resources of the respective\u00a0OS<\/span>\u00a0versions if you experience any issues<\/span><\/strong><\/pre>\n
Debian 6\/7\/8 and\u00a0<\/span>derivatives<\/span><\/h4>\n
Step 1 Create a\u00a0<\/span>backup<\/span><\/h5>\n
First, make a copy of the config file, so that you can revert at any\u00a0<\/span>time:<\/span><\/p>\n
# cp \/etc\/network\/interfaces \/etc\/network\/interfaces.bak<\/span><\/strong><\/pre>\n
Step 2 Edit the config\u00a0<\/span>file<\/span><\/h5>\n
Note that the names of the network interfaces in our examples may differ from your own. Please adjust to your appropriate interface names.<\/span><\/strong><\/pre>\n
You can now modify the config\u00a0<\/span>file:<\/span><\/p>\n
# nano\u00a0\/etc\/network\/interfaces<\/span><\/strong><\/pre>\n
You then need to add a secondary\u00a0<\/span>interface:<\/span><\/p>\n
auto eth0:0\niface eth0:0 inet static\naddress ADDITIONAL_IP\nnetmask 255.255.255.255<\/span><\/strong><\/pre>\n
To ensure that the secondary interface is enabled or disabled whenever the\u00a0eth0<\/strong> interface is enabled or disabled, you need to add the following line to the eth0<\/strong> configuration:<\/span><\/p>\n
# post-up \/sbin\/ifconfig eth0:0 ADDITIONAL_IP netmask 255.255.255.255 broadcast ADDITIONAL_IP\n# pre-down \/sbin\/ifconfig eth0:0 down<\/span><\/strong><\/pre>\n
If you have two additional IPs to configure, the \/etc\/network\/interfaces<\/strong><\/em> file should look like\u00a0<\/span>this:<\/span><\/p>\n
auto eth0\niface eth0 inet static\naddress SERVER_IP\nnetmask 255.255.255.0\nbroadcast xxx.xxx.xxx.255\ngateway xxx.xxx.xxx.254\n\nauto eth0:0\niface eth0:0 inet static\naddress ADDITIONAL_IP 1\nnetmask 255.255.255.255\n\nauto eth0:1\niface eth0:1 inet static\naddress ADDITIONAL_IP 2\nnetmask 255.255.255.255<\/span><\/strong><\/pre>\n
Or like this:<\/span><\/p>\n
auto eth0\niface eth0 inet static\naddress SERVER_IP\nnetmask 255.255.255.0\nbroadcast xxx.xxx.xxx.255\ngateway xxx.xxx.xxx.254\n\n# ADDITIONAL_IP 1<\/span>\npost-up \/sbin\/ifconfig eth0:0 FAILOVER_IP1 netmask 255.255.255.255 broadcast ADDITIONAL_IP 1\npre-down \/sbin\/ifconfig eth0:0 down\n\n# ADDITIONAL_IP 2<\/span>\npost-up \/sbin\/ifconfig eth0:1 FAILOVER_IP2 netmask 255.255.255.255 broadcast ADDITIONAL_IP 2<\/span>\npre-down \/sbin\/ifconfig eth0:1 down<\/span><\/strong><\/pre>\n
Step 3 Restart the\u00a0<\/span>interface<\/span><\/h5>\n
You now need to restart your\u00a0<\/span>interface:<\/span><\/p>\n
# \/etc\/init.d\/networking restart<\/span><\/strong><\/pre>\n
Debian 9+, Ubuntu 17.04, Fedora 26+ and Arch\u00a0<\/span>Linux<\/span><\/h4>\n
On these distributions, the naming of interfaces as eth0, eth1 (and so on) is abolished. We will therefore use\u00a0systemd-network<\/strong>\u00a0more generally.<\/span><\/p>\n
Step 1 Create a\u00a0<\/span>backup<\/span><\/h5>\n
First, make a copy of the config file, so that you can revert at any\u00a0<\/span>time:<\/span><\/p>\n
# cp \/etc\/systemd\/network\/50-default.network \/etc\/systemd\/network\/50-default.network.bak<\/span><\/strong><\/pre>\n
Step 2 Edit the config\u00a0<\/span>file<\/span><\/h5>\n
You can now add your additional IP<\/span>\u00a0to the config file, as\u00a0<\/span>follows:<\/span><\/p>\n
# nano \/etc\/systemd\/network\/50-default.network<\/span><\/strong><\/pre>\n
[<\/span>Address]<\/span>\nAddress<\/span>=ADDITIONAL_IP<\/span>\/32\nLabel<\/span>=ADDITIONAL_IP<\/span> # optional<\/span><\/span><\/strong><\/pre>\n
The label is optional. It\u2019s just for distinguishing between your various additional\u00a0<\/span>IPs.<\/span><\/p>\n
Step 3 Restart the\u00a0<\/span>interface<\/span><\/h5>\n
You now need to restart your\u00a0<\/span>interface:<\/span><\/p>\n
# systemctl restart systemd-networkd<\/span><\/strong><\/pre>\n
Ubuntu 17.10 and\u00a0<\/span>following<\/span><\/h4>\n
Each additional IP<\/span>\u00a0address will need its own line in the configuration file. The configuration file is called \u201c50-cloud-init.yaml\u201d<\/strong> and is located in\u00a0<\/span>\/etc\/netplan<\/strong><\/em>.<\/span><\/p>\n
Step 1 Determine the\u00a0<\/span>interface<\/span><\/h5>\n
# ifconfig<\/span><\/strong><\/pre>\n
Note the interface name and its\u00a0MAC<\/span>\u00a0<\/span>address.<\/span><\/p>\n
Step 2 Create the configuration\u00a0<\/span>file<\/span><\/h5>\n
Connect to your server via\u00a0SSH<\/span>\u00a0and run the following\u00a0<\/span>command:<\/span><\/p>\n
# nano\u00a0\/etc\/netplan\/50-cloud-init.yaml<\/span><\/strong><\/pre>\n
Next, edit the file with the content below, replacing INTERFACE_NAME<\/strong> MAC_ADDRESS<\/strong> and ADDITIONAL_IP<\/strong>:<\/span><\/p>\n
network:\n    version: 2\n    ethernets:\n        INTERFACE_NAME:\n            dhcp4: true<\/span>\n            match:\n                macaddress: MAC_ADDRESS\n            set-name: INTERFACE_NAME\n            addresses:\n            - ADDITIONAL_IP\/32<\/span><\/strong><\/pre>\n
Save and close the file. You can test the configuration with the following\u00a0<\/span>command:<\/span><\/p>\n
# netplan try<\/span><\/strong><\/pre>\n
Step 3 Apply the\u00a0<\/span>change<\/span><\/h5>\n
Next, run the following commands to apply the\u00a0<\/span>configuration:<\/span><\/p>\n
# netplan apply<\/span><\/strong><\/pre>\n
CentOS and Fedora (25 and\u00a0<\/span>earlier)<\/span><\/h4>\n
Step 1 Create the config\u00a0<\/span>file<\/span><\/h5>\n
First, make a copy of the source file so that you can use it as a\u00a0<\/span>template:<\/span><\/p>\n
# cp \/etc\/sysconfig\/network-scripts\/ifcfg-eth0 \/etc\/sysconfig\/network-scripts\/ifcfg-eth0:0<\/span><\/strong><\/pre>\n
Step 2 Edit the config\u00a0<\/span>file<\/span><\/h5>\n
You can now modify the eth0:0<\/strong> file in order to replace the\u00a0<\/span>IP<\/span>:<\/span><\/p>\n
# nano \/etc\/sysconfig\/network-scripts\/ifcfg-eth0:0<\/span><\/strong><\/pre>\n
First, replace the name of the\u00a0device<\/strong>, then replace the existing\u00a0IP<\/span> with the additional IP<\/span>\u00a0you have\u00a0<\/span>received:<\/span><\/p>\n
DEVICE<\/span>=<\/span>\"eth0:0\"<\/span>\nONBOOT<\/span>=<\/span>\"yes\"<\/span>\nBOOTPROTO<\/span>=<\/span>\"none\"<\/span> # For CentOS use \"static\"<\/span>\nIPADDR<\/span>=<\/span>\"ADDITIONAL_IP\"<\/span>\nNETMASK<\/span>=<\/span>\"255.255.255.255\"<\/span>\nBROADCAST<\/span>=<\/span>\"ADDITIONAL_IP\"<\/span><\/span><\/strong><\/pre>\n
Step 3 Start the alias\u00a0<\/span>interface<\/span><\/h5>\n
You now need to start your alias\u00a0<\/span>interface:<\/span><\/p>\n
# ifup eth0:0<\/span><\/strong><\/pre>\n
Gentoo<\/span><\/h4>\n
Step 1 Create a\u00a0<\/span>backup<\/span><\/h5>\n
First, make a copy of the config file, so that you can revert at any\u00a0<\/span>time:<\/span><\/p>\n
# cp \/etc\/conf.d\/net \/etc\/conf.d\/net.bak<\/span><\/strong><\/pre>\n
Step 2 Edit the config\u00a0<\/span>file<\/span><\/h5>\n
Now you have to edit the file to add the additional IP<\/span>. In Gentoo, an alias is added directly in the eth0<\/strong> interface. You do not need to create an eth0:0<\/strong> interface like in other\u00a0<\/span>distributions.<\/span><\/p>\n
The server\u2019s default\u00a0IP<\/span> and config_eth0=\u00a0 should stay on the same line.<\/span><\/strong><\/pre>\n
All you need to do is add a line break after the netmask\u00a0255.255.255.0<\/strong> and add your additional IP<\/span>\u00a0(SERVER_IP must be replaced by your server\u2019s primary\u00a0<\/span>IP<\/span>).<\/span><\/p>\n
# nano \/etc\/conf.d\/net<\/span><\/strong><\/pre>\n
You therefore need to add the\u00a0<\/span>following:<\/span><\/p>\n
config_eth0<\/span>=(<\/span> \"SERVER_IP netmask 255.255.255.0\"<\/span> \"ADDITIONAL_IP netmask 255.255.255.255 brd ADDITIONAL_IP\"<\/span> )<\/span><\/span><\/strong><\/pre>\n
The\u00a0\/etc\/conf.d\/ <\/strong><\/em>net\u00a0file must contain the\u00a0following:<\/span><\/p>\n
#This blank configuration will automatically use DHCP for any net.<\/span>\n# scripts in \/etc\/init.d. To create a more complete configuration,<\/span>\n# please review \/etc\/conf.d\/net.example and save your configuration<\/span>\n# in \/etc\/conf.d\/net (this file :]!).<\/span>\nconfig_eth0<\/span>=(<\/span> \"SERVER_IP netmask 255.255.255.0\"<\/span>\n\"ADDITIONAL_IP netmask 255.255.255.255 brd ADDITIONAL_IP\"<\/span> )<\/span>\nroutes_eth0<\/span>=(<\/span> \"default gw SERVER_IP.254\"<\/span> )<\/span><\/span><\/strong><\/pre>\n
In order to ping your additional IP<\/span>, simply restart the network\u00a0<\/span>interface.<\/span><\/p>\n
Step 3 Restart the\u00a0<\/span>interface<\/span><\/h5>\n
You now need to restart your\u00a0<\/span>interface:<\/span><\/p>\n
# \/etc\/init.d\/net.eth0 restart<\/span><\/strong><\/pre>\n
openSUSE<\/span><\/h4>\n
Step 1 Create a\u00a0<\/span>backup<\/span><\/h5>\n
First, make a copy of the config file, so that you can revert at any\u00a0<\/span>time:<\/span><\/p>\n
# cp \/etc\/sysconfig\/network\/ifcfg-ens32 \/etc\/sysconfig\/network\/ifcfg-ens32.bak<\/span><\/strong><\/pre>\n
Step 2 Edit the config\u00a0<\/span>file<\/span><\/h5>\n
Open the file:<\/span><\/p>\n
# nano \/etc\/sysconfig\/network\/ifcfg-ens32<\/span><\/strong><\/pre>\n
Then add the\u00a0<\/span>following:<\/span><\/p>\n
IPADDR_1<\/span>=ADDITIONAL_IP<\/span>\nNETMASK_1<\/span>=<\/span>255.255.255.255\nLABEL_1<\/span>=<\/span>ens32:0<\/span><\/strong><\/pre>\n
Finally, reboot your server to apply the\u00a0<\/span>changes.<\/span><\/p>\n
cPanel (on CentOS\u00a0<\/span>6)<\/span><\/h4>\n
Step 1 Create a\u00a0<\/span>backup<\/span><\/h5>\n
First, make a copy of the config file, so that you can revert at any\u00a0<\/span>time:<\/span><\/p>\n
# cp \/etc\/ips \/etc\/ips.bak<\/span><\/strong><\/pre>\n
Step 2 Edit the config\u00a0<\/span>file<\/span><\/h5>\n
You then need to edit the \/etc\/ips<\/strong><\/em>\u00a0file:<\/span><\/p>\n
# nano editor \/etc\/ips<\/span><\/strong><\/pre>\n
Then add the additional IP<\/span>\u00a0to the\u00a0<\/span>file:<\/span><\/p>\n
ADDITIONAL_IP:255.255.255.255:ADDITIONAL_IP<\/span><\/strong><\/pre>\n
Next, add the\u00a0IP\u00a0in \/etc\/ipaddrpool:<\/strong><\/em><\/span><\/p>\n
ADDITIONAL_IP<\/span><\/strong><\/pre>\n
Step 3 Restart the\u00a0<\/span>interface<\/span><\/h5>\n
You now need to restart your\u00a0<\/span>interface:<\/span><\/p>\n
# \/etc\/init.d\/ipaliases restart<\/span><\/strong><\/pre>\n
Windows Servers<\/span><\/h4>\n
Windows servers are often\u00a0DHCP<\/span>-enabled in the network configuration. If you have already set up a additional IP<\/span>\u00a0or switched your configuration to a fixed\u00a0IP<\/span>, go directly to the next\u00a0<\/span>step.<\/span><\/p>\n
Otherwise, you need to first switch from a network-level\u00a0DHCP<\/span>\u00a0configuration to a fixed\u00a0IP<\/span>\u00a0<\/span>configuration.<\/span><\/p>\n
Open the command prompt\u00a0cmd<\/strong>\u00a0or\u00a0powershell<\/strong>, then type the following\u00a0command:<\/span><\/p>\n
ipconfig \/all<\/span><\/strong><\/pre>\n
This will return a result similar to the following\u00a0<\/span>example:<\/span><\/p>\n
\"Configuring<\/p>\n
Identify and write down your IPv4, subnet mask, default gateway and the name of the network interface controller (network\u00a0<\/span>adapter).<\/span><\/p>\n
In our example, the server\u00a0IP<\/span>\u00a0is\u00a094.23.229.151<\/strong>.<\/span><\/p>\n
You can perform the next steps via either a command-line interface or the graphical user\u00a0<\/span>interface.<\/span><\/p>\n
Via a command-line interface\u00a0<\/span>(recommended)<\/span><\/h5>\n
In the commands below, you need to\u00a0<\/span>replace:<\/span><\/p>\n\n\n
Command<\/strong><\/td>Value<\/strong><\/td><\/tr>
NETWORK_ADAPTER<\/td>Name of the network adapter (in our example: Local Area Connection)<\/td><\/tr>
IP_ADDRESS<\/td>Server IP address (in our example: 94.23.229.151)<\/td><\/tr>
SUBNET_MASK<\/td>Subnet mask (in our example: 255.255.255.0)<\/td><\/tr>
GATEWAY<\/td>Default gateway (in our example: 94.23.229.254)<\/td><\/tr>
ADDITIONAL_IP<\/td>Address IP you want to add<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n
Be careful \u2013 the server will no longer be accessible if you enter incorrect information. You will then have to make the corrections in Winrescue mode or via the\u00a0KVM<\/span>.<\/span><\/strong><\/pre>\n
In the command\u00a0<\/span>prompt<\/span><\/h5>\n
Switch to a fixed\u00a0IP:<\/span><\/p>\n
netsh interface ipv4 set<\/span> address name<\/span>=<\/span>\"NETWORK_ADAPTER\"<\/span> static IP_ADDRESS SUBNET_MASK GATEWAY<\/span><\/strong><\/pre>\n
Set the\u00a0DNS<\/span>\u00a0<\/span>server:
<\/span><\/p>\n
netsh interface ipv4 set<\/span> dns name<\/span>=<\/span>\"NETWORK_ADAPTER\"<\/span> static 213.186.33.99<\/span><\/strong><\/pre>\n
Add additional \u00a0<\/span>IP:<\/span><\/span><\/p>\n
netsh interface ipv4 add address \"NETWORK_ADAPTER\"<\/span> ADDITIONAL_IP 255.255.255.255<\/span><\/strong><\/pre>\n
Your additional IP<\/span>\u00a0is now\u00a0<\/span>functional.<\/span><\/p>\n
Via the graphical user\u00a0<\/span>interface<\/span><\/h5>\n
    \n
  1. Go to\u00a0Start <\/strong>>\u00a0Control Panel <\/strong>> Network and Internet <\/strong>>\u00a0Network and Sharing Centre <\/strong>>\u00a0Change Adapter Settings<\/strong>(in the left-hand\u00a0menu).<\/span><\/li>\n
  2. Right-click on\u00a0Local Area Connection<\/strong>.<\/span><\/li>\n
  3. Click on\u00a0Properties<\/strong>.<\/span><\/li>\n
  4. Select\u00a0Internet Protocol Version 4 (TCP\/IPv4<\/strong>), then click on\u00a0Properties<\/strong>.<\/span><\/li>\n
  5. Click on\u00a0Use the following IP address<\/strong>\u00a0and type in your server\u2019s primary\u00a0IP, subnet mask and default gateway information obtained by using the\u00a0ipconfig<\/strong>\u00a0command above. In the \u201cPreferred\u00a0DNS\u00a0Server\u201d<\/strong> box, type\u00a0213.186.33.99.<\/span><\/li>\n<\/ol>\n
    \"Configuring<\/p>\n
    Be careful \u2013 the server will no longer be accessible if you enter incorrect information. You will then have to make the corrections in Winrescue mode or via the\u00a0KVM<\/span>.<\/span><\/strong><\/pre>\n
    Then click on\u00a0Advanced<\/strong>\u00a0(still in the\u00a0TCP\/IP Settings<\/strong>).<\/span><\/p>\n
    \"Configuring<\/p>\n
    In the\u00a0IP Address<\/strong>\u00a0section, click\u00a0Add<\/strong>:<\/span><\/p>\n
    \"Configuring<\/p>\n
    Type in your additional IP<\/span>\u00a0and the subnet mask\u00a0255.255.255.255:<\/strong><\/span><\/p>\n
    \"Configuring<\/p>\n
    Click on\u00a0Add<\/strong>.<\/span><\/p>\n
    Your additional IP<\/span>\u00a0is now\u00a0<\/span>functional.<\/span><\/p>\n
    FreeBSD<\/span><\/h4>\n
    Step 1 Determine the\u00a0<\/span>interface<\/span><\/h5>\n
    Determine the name of your primary network interface. You can use the\u00a0ifconfig<\/strong>\u00a0command for this\u00a0operation:<\/span><\/p>\n
    # ifconfig<\/span><\/strong><\/pre>\n
    This will return the\u00a0<\/span>following:<\/span><\/p>\n
    ifconfig\n>>> nfe0: flags<\/span>=<\/span>8843<\/span> metric 0<\/span> mtu 1500\n>>> options<\/span>=<\/span>10b\n>>> ether 00:24:8c:d7:ba:11\n>>> inet 94.23.196.18 netmask 0xffffff00 broadcast 94.23.196.255\n>>> inet 87.98.129.74 netmask 0xffffffff broadcast 87.98.129.74\n>>> media: Ethernet autoselect (<\/span>100baseTX )<\/span>\n>>> status: active\n>>> lo0: flags<\/span>=<\/span>8049<\/span> metric 0<\/span> mtu 16384\n>>> options<\/span>=<\/span>3\n>>> inet6 fe80::1%lo0 prefixlen 64<\/span> scopeid 0x2\n>>> inet6 ::1 prefixlen 128\n>>> inet 127.0.0.1 netmask 0xff000000 v comsdvt#<\/span><\/strong><\/pre>\n
    In our example, the name of the interface is therefore\u00a0nfe0<\/strong>.<\/span><\/p>\n
    Step 2 Create a\u00a0<\/span>backup<\/span><\/h5>\n
    Next, make a copy of the config file, so that you can revert at any\u00a0<\/span>time:<\/span><\/p>\n
    # cp \/etc\/rc.conf \/etc\/rc.conf.bak<\/span><\/strong><\/pre>\n
    Step 3 Edit the config\u00a0<\/span>file<\/span><\/h5>\n
    Edit the \/etc\/rc.conf<\/strong><\/em>\u00a0<\/span>file:<\/span><\/p>\n
    # nano \/etc\/rc.conf<\/span><\/strong><\/pre>\n
    Then add this line at the end of the file:\u00a0ifconfig_INTERFACE_alias0=”inet ADDITIONAL_IP netmask 255.255.255.255 broadcast ADDITIONAL_IP”.<\/strong><\/span><\/p>\n
    Replace\u00a0INTERFACE<\/strong> and ADDITIONAL_IP<\/strong> with the name of your interface (identified in the first step) and your additional IP, respectively. Here is an\u00a0example:<\/span><\/p>\n
    # ifconfig_nfe0_alias0<\/span>=<\/span>\"inet 87.98.129.74 netmask 255.255.255.255 broadcast 87.98.129.74\"<\/span><\/span><\/strong><\/pre>\n
    Step 4 Restart the\u00a0<\/span>interface<\/span><\/h5>\n
    You now need to restart your\u00a0<\/span>interface:<\/span><\/p>\n
    # \/etc\/rc.d\/netif restart &&<\/span> \/etc\/rc.d\/routing restart<\/span><\/strong><\/pre>\n
    Solaris<\/span><\/h4>\n
    Step 1 Determine the\u00a0<\/span>interface<\/span><\/h5>\n
    Determine the name of your primary network interface. You can use the\u00a0ifconfig<\/strong>\u00a0command for this\u00a0operation:<\/span><\/p>\n
    # ifconfig -a<\/span><\/strong><\/pre>\n
    This will return the\u00a0<\/span>following:<\/span><\/p>\n
    ifconfig -a\nlo0:     flags<\/span>=<\/span>2001000849<\/span> mtu 8232<\/span> index 1<\/span> \n         inet 127.0.0.1 netmask ff000000 \ne1000g0: flags<\/span>=<\/span>1000843<\/span> mtu 1500<\/span> index 2<\/span> \n         inet 94.23.41.167 netmask ffffff00 broadcast 94.23.41.255 \n         ether 0:1c:c0:f2:be:42<\/span><\/strong><\/pre>\n
    In our example, the name of the interface is therefore\u00a0e1000g0<\/strong>.<\/span><\/p>\n
    Step 2 Create the config\u00a0<\/span>file<\/span><\/h5>\n
    # nano \/etc\/hostname.e1000g0:1<\/span><\/strong><\/pre>\n
    In this file, enter the following: ADDITIONAL_IP\/32<\/strong> up, where ADDITIONAL_IP<\/strong> is your additional IP. For\u00a0example:<\/span><\/p>\n
    188.165.171.40\/32 up<\/span><\/strong><\/pre>\n
    Step 3 Restart the\u00a0<\/span>interface<\/span><\/h5>\n
    You now need to restart your\u00a0<\/span>interface:<\/span><\/p>\n
    # svcadm restart svc:\/network\/physical:default<\/span><\/strong><\/pre>\n
    Troubleshooting<\/span><\/h4>\n
    If you are unable to establish a connection from the public network to your alias\u00a0IP<\/span>\u00a0and suspect a network problem, please reboot the server in Rescue Mode<\/strong> and setup the alias directly on the\u00a0<\/span>server.<\/span><\/p>\n
    In order to do that, once you\u2019ve rebooted your server in Rescue Mode<\/strong>, please do the following\u00a0<\/span>command:<\/span><\/p>\n
    # ifconfig eth0:0 ADDITIONAL_IP netmask 255.255.255.255 broadcast ADDITIONAL_IP up<\/span><\/strong><\/pre>\n
    Where you will replace ADDITIONAL_IP<\/strong> by the actual additional <\/span>IP.<\/span><\/span><\/p>\n
    Next, simply ping your\u00a0additional IP\u00a0from the outside. If it works, it probably means that there is a configuration error that requires to be fixed. If, on the contrary, the\u00a0IP\u00a0is still not working, please inform our support team by creating a support request in your\u00a0Client Area<\/em><\/a><\/span><\/p>\n\n\n
    <\/p>\n","protected":false},"excerpt":{"rendered":"
    IP aliasing is a special network configuration for your dedicated servers you to associate multiple IP\u00a0addresses with a single network\u00a0interface.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[158],"tags":[520,521],"class_list":["post-2663","post","type-post","status-publish","format-standard","hentry","category-dedicated-servers","tag-dedicated-servers","tag-ip"],"yoast_head":"\nConfiguring IP aliasing - Unihost.FAQ<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/unihost.com\/help\/network-ip-aliasing\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Configuring IP aliasing - Unihost.FAQ\" \/>\n<meta property=\"og:description\" content=\"IP aliasing is a special network configuration for your dedicated servers you to associate multiple IP\u00a0addresses with a single network\u00a0interface.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/unihost.com\/help\/network-ip-aliasing\/\" \/>\n<meta property=\"og:site_name\" content=\"Unihost.FAQ\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/unihost\/\" \/>\n<meta property=\"article:published_time\" content=\"2015-11-12T22:58:23+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2024-12-13T10:59:35+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/unihost.com\/help\/wp-content\/uploads\/Screenshot-at-13-34-43.png\" \/>\n<meta name=\"author\" content=\"Unihost Support\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@unihost\" \/>\n<meta name=\"twitter:site\" content=\"@unihost\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Unihost Support\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/unihost.com\/help\/network-ip-aliasing\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/unihost.com\/help\/network-ip-aliasing\/\"},\"author\":{\"name\":\"Unihost Support\",\"@id\":\"https:\/\/unihost.com\/help\/#\/schema\/person\/bb5ae95f38577c920e6a7507888b715a\"},\"headline\":\"Configuring IP aliasing\",\"datePublished\":\"2015-11-12T22:58:23+00:00\",\"dateModified\":\"2024-12-13T10:59:35+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/unihost.com\/help\/network-ip-aliasing\/\"},\"wordCount\":1270,\"publisher\":{\"@id\":\"https:\/\/unihost.com\/help\/#organization\"},\"image\":{\"@id\":\"https:\/\/unihost.com\/help\/network-ip-aliasing\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/unihost.com\/help\/wp-content\/uploads\/Screenshot-at-13-34-43.png\",\"keywords\":[\"dedicated servers\",\"IP\"],\"articleSection\":[\"02. Dedicated servers\"],\"inLanguage\":\"en\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/unihost.com\/help\/network-ip-aliasing\/\",\"url\":\"https:\/\/unihost.com\/help\/network-ip-aliasing\/\",\"name\":\"Configuring IP aliasing - Unihost.FAQ\",\"isPartOf\":{\"@id\":\"https:\/\/unihost.com\/help\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/unihost.com\/help\/network-ip-aliasing\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/unihost.com\/help\/network-ip-aliasing\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/unihost.com\/help\/wp-content\/uploads\/Screenshot-at-13-34-43.png\",\"datePublished\":\"2015-11-12T22:58:23+00:00\",\"dateModified\":\"2024-12-13T10:59:35+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/unihost.com\/help\/network-ip-aliasing\/#breadcrumb\"},\"inLanguage\":\"en\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/unihost.com\/help\/network-ip-aliasing\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en\",\"@id\":\"https:\/\/unihost.com\/help\/network-ip-aliasing\/#primaryimage\",\"url\":\"https:\/\/unihost.com\/help\/minio.php?.\/Screenshot-at-13-34-43.png\",\"contentUrl\":\"https:\/\/unihost.com\/help\/minio.php?.\/Screenshot-at-13-34-43.png\",\"width\":642,\"height\":222},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/unihost.com\/help\/network-ip-aliasing\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Unihost\",\"item\":\"https:\/\/unihost.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Help\",\"item\":\"https:\/\/unihost.com\/help\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Configuring IP aliasing\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/unihost.com\/help\/#website\",\"url\":\"https:\/\/unihost.com\/help\/\",\"name\":\"Unihost.FAQ\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/unihost.com\/help\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/unihost.com\/help\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/unihost.com\/help\/#organization\",\"name\":\"Unihost\",\"alternateName\":\"Unihost\",\"url\":\"https:\/\/unihost.com\/help\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en\",\"@id\":\"https:\/\/unihost.com\/help\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/unihost.com\/help\/minio.php?2026\/01\/minio.png\",\"contentUrl\":\"https:\/\/unihost.com\/help\/minio.php?2026\/01\/minio.png\",\"width\":300,\"height\":300,\"caption\":\"Unihost\"},\"image\":{\"@id\":\"https:\/\/unihost.com\/help\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/unihost\/\",\"https:\/\/x.com\/unihost\",\"https:\/\/www.instagram.com\/unihost\/?hl=en\",\"https:\/\/www.linkedin.com\/company\/unihost-com\",\"https:\/\/www.youtube.com\/channel\/UCITKsxMDnslQY8brN3advgw\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/unihost.com\/help\/#\/schema\/person\/bb5ae95f38577c920e6a7507888b715a\",\"name\":\"Unihost Support\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en\",\"@id\":\"https:\/\/unihost.com\/help\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/a0c9db17c2a0d93e8a0d5ac123f8c5db750ad4d3d5657369c0c4e480f5af77b8?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/a0c9db17c2a0d93e8a0d5ac123f8c5db750ad4d3d5657369c0c4e480f5af77b8?s=96&d=mm&r=g\",\"caption\":\"Unihost Support\"},\"sameAs\":[\"https:\/\/unihost.com\/\"],\"url\":\"https:\/\/unihost.com\/help\/author\/support\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Configuring IP aliasing - Unihost.FAQ","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/unihost.com\/help\/network-ip-aliasing\/","og_locale":"en_US","og_type":"article","og_title":"Configuring IP aliasing - Unihost.FAQ","og_description":"IP aliasing is a special network configuration for your dedicated servers you to associate multiple IP\u00a0addresses with a single network\u00a0interface.","og_url":"https:\/\/unihost.com\/help\/network-ip-aliasing\/","og_site_name":"Unihost.FAQ","article_publisher":"https:\/\/www.facebook.com\/unihost\/","article_published_time":"2015-11-12T22:58:23+00:00","article_modified_time":"2024-12-13T10:59:35+00:00","og_image":[{"url":"https:\/\/unihost.com\/help\/wp-content\/uploads\/Screenshot-at-13-34-43.png","type":"","width":"","height":""}],"author":"Unihost Support","twitter_card":"summary_large_image","twitter_creator":"@unihost","twitter_site":"@unihost","twitter_misc":{"Written by":"Unihost Support","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/unihost.com\/help\/network-ip-aliasing\/#article","isPartOf":{"@id":"https:\/\/unihost.com\/help\/network-ip-aliasing\/"},"author":{"name":"Unihost Support","@id":"https:\/\/unihost.com\/help\/#\/schema\/person\/bb5ae95f38577c920e6a7507888b715a"},"headline":"Configuring IP aliasing","datePublished":"2015-11-12T22:58:23+00:00","dateModified":"2024-12-13T10:59:35+00:00","mainEntityOfPage":{"@id":"https:\/\/unihost.com\/help\/network-ip-aliasing\/"},"wordCount":1270,"publisher":{"@id":"https:\/\/unihost.com\/help\/#organization"},"image":{"@id":"https:\/\/unihost.com\/help\/network-ip-aliasing\/#primaryimage"},"thumbnailUrl":"https:\/\/unihost.com\/help\/wp-content\/uploads\/Screenshot-at-13-34-43.png","keywords":["dedicated servers","IP"],"articleSection":["02. Dedicated servers"],"inLanguage":"en"},{"@type":"WebPage","@id":"https:\/\/unihost.com\/help\/network-ip-aliasing\/","url":"https:\/\/unihost.com\/help\/network-ip-aliasing\/","name":"Configuring IP aliasing - Unihost.FAQ","isPartOf":{"@id":"https:\/\/unihost.com\/help\/#website"},"primaryImageOfPage":{"@id":"https:\/\/unihost.com\/help\/network-ip-aliasing\/#primaryimage"},"image":{"@id":"https:\/\/unihost.com\/help\/network-ip-aliasing\/#primaryimage"},"thumbnailUrl":"https:\/\/unihost.com\/help\/wp-content\/uploads\/Screenshot-at-13-34-43.png","datePublished":"2015-11-12T22:58:23+00:00","dateModified":"2024-12-13T10:59:35+00:00","breadcrumb":{"@id":"https:\/\/unihost.com\/help\/network-ip-aliasing\/#breadcrumb"},"inLanguage":"en","potentialAction":[{"@type":"ReadAction","target":["https:\/\/unihost.com\/help\/network-ip-aliasing\/"]}]},{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/unihost.com\/help\/network-ip-aliasing\/#primaryimage","url":"https:\/\/unihost.com\/help\/minio.php?.\/Screenshot-at-13-34-43.png","contentUrl":"https:\/\/unihost.com\/help\/minio.php?.\/Screenshot-at-13-34-43.png","width":642,"height":222},{"@type":"BreadcrumbList","@id":"https:\/\/unihost.com\/help\/network-ip-aliasing\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Unihost","item":"https:\/\/unihost.com\/"},{"@type":"ListItem","position":2,"name":"Help","item":"https:\/\/unihost.com\/help\/"},{"@type":"ListItem","position":3,"name":"Configuring IP aliasing"}]},{"@type":"WebSite","@id":"https:\/\/unihost.com\/help\/#website","url":"https:\/\/unihost.com\/help\/","name":"Unihost.FAQ","description":"","publisher":{"@id":"https:\/\/unihost.com\/help\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/unihost.com\/help\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en"},{"@type":"Organization","@id":"https:\/\/unihost.com\/help\/#organization","name":"Unihost","alternateName":"Unihost","url":"https:\/\/unihost.com\/help\/","logo":{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/unihost.com\/help\/#\/schema\/logo\/image\/","url":"https:\/\/unihost.com\/help\/minio.php?2026\/01\/minio.png","contentUrl":"https:\/\/unihost.com\/help\/minio.php?2026\/01\/minio.png","width":300,"height":300,"caption":"Unihost"},"image":{"@id":"https:\/\/unihost.com\/help\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/unihost\/","https:\/\/x.com\/unihost","https:\/\/www.instagram.com\/unihost\/?hl=en","https:\/\/www.linkedin.com\/company\/unihost-com","https:\/\/www.youtube.com\/channel\/UCITKsxMDnslQY8brN3advgw"]},{"@type":"Person","@id":"https:\/\/unihost.com\/help\/#\/schema\/person\/bb5ae95f38577c920e6a7507888b715a","name":"Unihost Support","image":{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/unihost.com\/help\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/a0c9db17c2a0d93e8a0d5ac123f8c5db750ad4d3d5657369c0c4e480f5af77b8?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/a0c9db17c2a0d93e8a0d5ac123f8c5db750ad4d3d5657369c0c4e480f5af77b8?s=96&d=mm&r=g","caption":"Unihost Support"},"sameAs":["https:\/\/unihost.com\/"],"url":"https:\/\/unihost.com\/help\/author\/support\/"}]}},"_links":{"self":[{"href":"https:\/\/unihost.com\/help\/wp-json\/wp\/v2\/posts\/2663","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/unihost.com\/help\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/unihost.com\/help\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/unihost.com\/help\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/unihost.com\/help\/wp-json\/wp\/v2\/comments?post=2663"}],"version-history":[{"count":47,"href":"https:\/\/unihost.com\/help\/wp-json\/wp\/v2\/posts\/2663\/revisions"}],"predecessor-version":[{"id":8454,"href":"https:\/\/unihost.com\/help\/wp-json\/wp\/v2\/posts\/2663\/revisions\/8454"}],"wp:attachment":[{"href":"https:\/\/unihost.com\/help\/wp-json\/wp\/v2\/media?parent=2663"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/unihost.com\/help\/wp-json\/wp\/v2\/categories?post=2663"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/unihost.com\/help\/wp-json\/wp\/v2\/tags?post=2663"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}