Skip to main content

Assign Virtual IPs to your NIC

Assigning a virtual IP to a NIC is a very easy task either you use the system-config-networktool or just do some text file editing. The script ifconfig can also be used to create a virtual network interface, but this would not be permanent since the changes ifconfig makes do not survive a reboot. In this post I’ll stick with the “manual” way…

In Fedora, all information about the network interfaces is kept in the following directories:

I assume that the default NIC configuration script is:
/etc/sysconfig/network-scripts/ifcfg-eth0. Mine looks like this:DEVICE=eth0 BOOTPROTO=static BROADCAST= HWADDR=00:00:00:00:00:00 IPADDR= NETMASK= NETWORK= ONBOOT=yes TYPE=Ethernet GATEWAY=

BOOTPROTO: sets the protocol that is used when the device is initialized. Since we use static IPs we set it to static.
HWADDR: is the MAC address of your network card. Do not change it. If this is missing in your configuration file, then don’t add it.
The rest of the options used are self-explanatory.

Make a copy of this in the same directory naming the new file ifcfg-eth0:1# cp ifcfg-eth0 ifcfg-eth0\:1

eth0:1 is an alias of the eth0 interface. Now, let’s assign a different IP address to eth0:1. Other NIC aliases could be named eth0:2, eth0:3 etc. Fire up your favourite text editor and edit ifcfg-eth0:1. The modifications are shown in bold:DEVICE=eth0:1 BOOTPROTO=static BROADCAST= HWADDR=00:00:00:00:00:00 IPADDR= NETMASK= NETWORK= ONBOOT=yes TYPE=Ethernet GATEWAY=

So, its IP address will be Save the file and copy it to/etc/sysconfig/networking/devices/:# cp ifcfg-eth0\:1 /etc/sysconfig/networking/devices/

Also, copy it to your default network profile or whichever profile you use:# cp ifcfg-eth0\:1 /etc/sysconfig/networking/profiles/default/

Now, bring up the new interface using the ifup script:# ifup eth0\:1

Running ifconfig, the new interface should be listed. You can also check it by pinging:# ping

You can now assign a host name on this virtual interface, by updating your local DNS server’s zone files or by adding it to the /etc/hosts files on all your LAN computers.

Popular posts from this blog


The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N