Typically, most VxWorks systems use the TCP/IP protocol suite. Although you can port other networking protocols to VxWorks, this document generally assumes you are using TCP/IP and the numerous networking components, utilities, and services built on TCP/IP. Included in the Internet Protocol suite are the transport layer protocols TCP and UDP. These protocols, along with OSPF (a separately purchasable option), are layered on top of the IP (network) layer. In turn, the IP layer rests on top of the MUX.

Also included in this section is a detailed description of ARP and proxy ARP.

VxWorks provides the MUX interface to support independence between the network protocol layer and the data link layer. To use a driver in the data link layer, the network protocol calls the appropriate MUX routine. Likewise, when a driver in the data link layer needs to access the network layer (whether IP or another protocol), it calls the appropriate MUX routine. Neither protocol nor driver deal with each other directly. Thus, neither needs specific knowledge of the other, which makes it easier to plug in a new protocol over existing drivers. For more information on the MUX interface, see the Network Protocol Toolkit User's Guide.

To attach the TCP/IP stack to the MUX for a particular interface, use the ipAttach( ) routine. When an interface is shut down, ipDetach( ) will release the TCP/IP stack components for that interface.