Administering Logical Network Interfaces

Logical interfaces are also referred to as virtual interfaces. You can configure an interface to have many different IP addresses, even IP addresses that are in different IP classes. This is one way that a single system can appear to be multiple systems.

Logical interfaces do not have to exist on the same subnet as the primary interface.

Each logical interface is assigned a unique IP address and a unique host name in cases in which:

• Systems use high-availability failover
• Web servers require multiple web site Universal Resource Locators (URLs)
• Servers run several applications that must appear as separate systems

Some advantages of logical interfaces are:

• Lower cost. You do not need to purchase additional Ethernet cards.
  
• Easier to back up and administer. Backup and maintenance can be done on one host instead of on several hosts.

Some disadvantages of logical interfaces are:

• Heavy network load. Having many logical addresses tied to a specific Ethernet interface can cause a network performance bottleneck.
• Slower system start. Each logical interface must be configured on system boot, which can be a lengthy process when a large number of interfaces are configured.

Physical network interfaces have names of the form:

driver-name physical-unit-number

For example: hme0, qfe3.

Logical interfaces have names of the form:

driver-name physical-unit-number:logical-unit-number

A system with one interface can appear as two different systems.

The /etc/hostname.interface File

The S30network.sh startup script at run level S reads the /etc/hostname.interface file. The ifconfig utility used within the script assigns an IPv4 address on the local system for each IPv4 interface. At least one /etc/hostname.interface  file must exist on the local system for each interface to be configured. The Solaris installation program creates this file only for the primary interface. Additional interfaces are configured by manually creating additional hostname.interface  files.

These files must contain at least one entry: the host name or the IPv4 address that is associated with the network interface.

For example, if the hme0 interface is the primary network interface for a system called myhost, the file is called /etc/hostname. hme0 and contains at least one line, which is the name of the system, myhost.

Configuring Logical Interfaces

After a physical interface is plumbed (has streams set up for IP and is open), and configured as up by the ifconfig utility, you can configure logical interfaces that are associated with the physical interface by separate plumb or addif options to the ifconfig utility.

To view the current configuration of the interfaces on the system before adding a logical interface, use the ifconfig utility:

# ifconfig -a

lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000

hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.30.31 netmask ffffff00 broadcast 192.168.30.255
ether 8:0:20:b9:72:23

qfe0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 192.168.1.1 netmask ffffff00 broadcast 192.168.1.255
ether 8:0:20:b9:72:23

To configure logical network interface 1 on the hme0 physical interface,  use the ifconfig utility. In this example, the logical interface is assigned  an IP address of 192.169.1.1:

# ifconfig hme0:1 plumb 192.169.1.1 up

To view the changes made to the interface, use the ifconfig utility:

# ifconfig -a

lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000

hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.30.31 netmask ffffff00 broadcast 192.168.30.255
ether 8:0:20:b9:72:23

hme0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.169.1.1 netmask ffffff00 broadcast 192.169.1.255

qfe0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 192.168.1.1 netmask ffffff00 broadcast 192.168.1.255
ether 8:0:20:b9:72:23

The hme0:1 interface is now configured, it has a default netmask of ffffff00 (255.255.255.0), and it has a broadcast address of  192.169.1.255.

You could have assigned different values if you wanted to. Notice that the index number is unique for each physical interface, while logical interfaces use the physical interface’s index number.

The addif Option

It can be tedious to increment the logical interface number each time you add logical interfaces. The ifconfig utility includes the addif option, which causes the utility to add the next available logical interface.

For example, to add the next logical interface with an IP address of 192.168.55.1, use a command similar to the following:

# ifconfig hme0 addif 192.168.55.1 up
Created new logical interface hme0:2

The same results can be achieved by editing the /etc/hostname.hme0 file so that its contents are similar to the following:

# cat /etc/hostname.hme0
myhost up
addif 192.168.55.1 up

Then reboot the system using  init 6 to configure the logical interface. To view the changes made to the interface, use the ifconfig utility:

# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000

hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.30.31 netmask ffffff00 broadcast 192.168.30.255
ether 8:0:20:b9:72:23

hme0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.55.1 netmask ffffff00 broadcast 192.168.55.255

qfe0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 192.168.1.1 netmask ffffff00 broadcast 192.168.1.255
ether 8:0:20:b9:72:23

The hme0:1 interface is added and is functional.

Unconfiguring Logical Interfaces

To unconfigure a logical interface, use the ifconfig utility with the down and unplumb options. Use the down option before the unplumb option to make sure that the interface is shut down in the proper order and that no data is lost. For example, to unconfigure the hme0:1 interface, enter the following:

# ifconfig hme0:1 down unplumb

To verify that the interface is removed, use the ifconfig utility:

# ifconfig -a

lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000

hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.30.31 netmask ffffff00 broadcast 192.168.30.255
ether 8:0:20:b9:72:23

hme0:2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.55.1 netmask ffffff00 broadcast 192.168.55.255

qfe0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 192.168.1.1 netmask ffffff00 broadcast 192.168.1.255
ether 8:0:20:b9:72:23

The hme0:1 interface is no longer available.

When you know the logical interface’s IP address, but you do not know to which logical interface the address is assigned, use the ifconfig with the removeif option. For example:

# ifconfig hme0 removeif 192.168.55.1

Note: If you are logged in remotely using this interface for your connection, you will lose connection to the system.

Etc

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotes :  Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce :  Bernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS :  Programming Languages History : PL/1 : Simula 67 : C : History of GCC development :  Scripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month :  How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: March 12, 2019