?? c-tcpip1.html
字號:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"><html><head><link rel="STYLESHEET" type="text/css" href="wrs.css"><title> TCP/IP Under VxWorks </title></head><body bgcolor="FFFFFF"><p class="navbar" align="right"><a href="index.html"><img border="0" alt="[Contents]" src="icons/contents.gif"></a><a href="c-tcpip.html"><img border="0" alt="[Index]" src="icons/index.gif"></a><a href="c-tcpip.html"><img border="0" alt="[Top]" src="icons/top.gif"></a><a href="c-tcpip.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="c-tcpip2.html"><img border="0" alt="[Next]" src="icons/next.gif"></a></p><font face="Helvetica, sans-serif" class="sans"><h3 class="H2"><i><a name="86167">4.1 Introduction</a></i></h3></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="86169"> </a>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.</p><dd><p class="Body"><a name="86174"> </a>Also included in this section is a detailed description of ARP and proxy ARP. </p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H3"><i><a name="94709">4.1.1 MUX, an Interface between the Data Link and Network Layers</a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="94711"> </a>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 <i class="title">Network Protocol Toolkit User's Guide</i>. </p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H4"><i><a name="94312">Attaching to the MUX</a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="94314"> </a>To attach the TCP/IP stack to the MUX for a particular interface, use the <b class="routine"><i class="routine">ipAttach</i></b><b>( )</b> routine. When an interface is shut down, <b class="routine"><i class="routine">ipDetach</i></b><b>( )</b> will release the TCP/IP stack components for that interface.</p></dl></dl><a name="foot"><hr></a><p class="navbar" align="right"><a href="index.html"><img border="0" alt="[Contents]" src="icons/contents.gif"></a><a href="c-tcpip.html"><img border="0" alt="[Index]" src="icons/index.gif"></a><a href="c-tcpip.html"><img border="0" alt="[Top]" src="icons/top.gif"></a><a href="c-tcpip.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="c-tcpip2.html"><img border="0" alt="[Next]" src="icons/next.gif"></a></p></body></html><!---by WRS Documentation (), Wind River Systems, Inc. conversion tool: Quadralay WebWorks Publisher 4.0.11 template: CSS Template, Jan 1998 - Jefro --->?? 快捷鍵說明
復制代碼
Ctrl + C
搜索代碼
Ctrl + F
全屏模式
F11
切換主題
Ctrl + Shift + D
顯示快捷鍵
?
增大字號
Ctrl + =
減小字號
Ctrl + -