The ip command is part of the iproute2 suite of TCP/IP networking utilities. It keeps trying to replace the old familiar ifconfig and route commands, which do what they do splendidly but are a bit limited for today's network environments. One thing ip can do that ifconfig cannot is assign multiple addresses to a single network interface. ifconfig can assign multiple aliases, such as eth0:0, eth0:1, and so forth, but then you must give each alias a separate configuration as though they are separate physical interfaces. ip adds addresses to a single interface like this:
# ip addr add 192.168.1.10/24 brd + dev eth0 # ip addr add 192.168.2.10/24 brd + dev eth0
brd + means "automatically set the broadcast address." View the results with this command:
$ ip addr show eth0 2: eth0:
If you run ifconfig to check your addresses, it will see only the first one.
This is a great way to get access to multiple subnets without having to create a herd of new configurations, or install multiple network interface cards. Another practical use for this is accessing a new server or router for the first time. Typically, these come with a default IP address. If it's on a different subnet, but on the same switch, you can quickly add a compatible address to your workstation and log in to the new device. When you're finished, remove the unwanted addresses like so:
# ip addr del 192.168.3.10/24 dev eth0
man ip is the best and most complete reference.
This article was first published on ServerWatch.com.
One of the ways around the issues of security and control that make some businesses wary of cloud computing is to build a private cloud -- one that remains within the corporate firewall and is wholly controlled internally. Private clouds also increase the agility of IT an organization's IT infrastructure and make it easier to roll out new technology projects. Download this eBook to get the facts behind the private cloud and learn how your organization can get started.