Virtual network interface

<h2 id="operating-system-level">Operating system level</h2>
<p>It is common for the operating system <a href="/facts/Kernel_(computer_science)/uEj4U3Rz">kernel</a> to maintain a table of virtual network interfaces in memory.  This may allow the system to store and operate on such information independently of the physical interface involved (or even whether it is a direct physical interface or for instance a tunnel or a bridged interface).  It may also allow processes on the system to interact concerning network connections in a more granular fashion than simply assuming a single amorphous Internet (of unknown capacity or performance).
</p><p><a href="/facts/W._Richard_Stevens/t5hCDFb3">W. Richard Stevens</a>, in volume 2 of his treatise entitled <a href="/facts/TCP/IP_Illustrated/kSudSD7V">TCP/IP Illustrated</a>, refers to the kernel's Virtual Interface Table in his discussion of multicast routing. For example, a <a href="/facts/IP_multicast/YklMRaV5">multicast router</a> may operate differently on interfaces that represent tunnels than on physical interfaces (e.g. it may only need to collect membership information for physical interfaces). Thus the virtual interface may need to divulge some specifics to the user, such as whether or not it represents a physical interface directly.<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a>
</p><p>In addition to allowing user space applications to refer to abstract network interface connections, in some systems, a virtual interface framework may allow processes to better coordinate the sharing of a given physical interface
(beyond the default operating system behavior) by hierarchically subdividing it into abstract interfaces with specified bandwidth limits and queueing models. This can imply restriction of the process, e.g. by inheriting a limited branch of such a hierarchy from which it may not stray.
</p><p>This extra layer of network abstraction is often unnecessary and may have a minor performance penalty.  However, it is also possible to use such a layer of abstraction to work around a performance bottleneck, indeed even to bypass the kernel for optimization purposes.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a>
</p>
<h2 id="application-level">Application level</h2>
<p>The term VIF has also been applied when the application virtualizes or abstracts network interfaces.  Since most software need not concern itself with the particulars of network interfaces, and since the desired abstraction may already be available through the operating system, its usage is rare.
</p>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Loopback/NvRL5LTG">Loopback</a></li>
<li><a href="/facts/Network_virtualization/aWUs94EW">Network virtualization</a></li>
<li><a href="/facts/Virtual_Interface_Architecture/RkTWQNMs">Virtual Interface Architecture</a></li></ul>

<h2 id="external-links">External links</h2>
<ul><li><a href="http://wiki.openwrt.org/doc/networking/network.interfaces">Linux Network Interfaces</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>W. Richard Stevens; Gary R. Wright (1995), TCP/IP Illustrated, Volume 2: The Implementation, Addison-Wesley, pp. 401–434, ISBN 0-201-63354-X <a href="0-201-63354-X" target="_blank">0-201-63354-X</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>Jin-Soo Kim; Kangho Kim; Sung-In Jung (2001), "Building a high-performance communication layer over virtual interface architecture on Linux clusters", Proceedings of the 15th international conference on Supercomputing, ACM, pp. 335–347, doi:10.1145/377792.377858, ISBN 158113410X, S2CID 947584, retrieved 2009-02-09 <a href="158113410X" target="_blank">158113410X</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
</ol>

Virtual network interface open-in-new

Virtual network interface