Home / server / Questions / 461533
In Process
prl77
Asked: 2012-12-29 12:37:28 +0800 CST

Persist IP address alias across reboots in CentOS/RHEL 6 using "ip" command

  • 772

I've always used the ifcfg-eth0:1 alias files to create additional addresses. However, in recent rhel documentation, it states that:

As the ip command of the iproute package now supports assigning multiple address to the same interface it is no longer necessary to use this method of binding multiple addresses to the same interface.

Furthermore, numerous answers and comments on this site mention that ifconfig is deprecated and that "ip" should be used instead. I'm fine using it for live changes, but how do I persist the changes across reboots without using the alias files?

linux

2 Answers

  1. Put them in /etc/sysconfig/network-scripts/ifcfg-eth0, with a 2 or 3 etc. after them, such as:

    IPADDR2=192.0.2.48
NETMASK2=255.255.255.0
IPADDR3=192.0.2.49
NETMASK3=255.255.255.0

    Unfortunately this seems to be undocumented (or I can't find it right now; it looks like Red Hat rearranged their web site yet again).

    • 21

  2. On the same page where you pulled that paragraph, it tells you to use NetworkManager to assign multiple IP address to one interface.

    For new installations, users should select the Manual method on the IPv4 or IPv6 tab in NetworkManager to assign multiple IP address to the same interface. For more information on using this tool, refer to Chapter 7, NetworkManager.

    This appears to edit your interface configuration to add:

    IPADDR2=IP address
PREFIX2=Netmask
GATEWAY2=Gateway

    For what it's worth, it also says that it is no longer necessary to use alias files, but that doesn't mean it doesn't work. (Especially if you need DHCP.) I personally would rather manage my network outside the GUI so you should be able to stop the NetworkManager service and continue business-as-usual with your alias files.

    The last option, would be to put your ip commands in /etc/rc.local to be executed at system start. Beware, though, that if the network service is restarted, these settings will not be persistent. This should only be considered as a last resort.

    Deployment Guide, 8.2.7. Alias and Clone Files

    • 6