📄 c-config1.html
字号:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"><html><head><link rel="STYLESHEET" type="text/css" href="wrs.css"><title> Configuring the VxWorks Network Stack </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-config.html"><img border="0" alt="[Index]" src="icons/index.gif"></a><a href="c-config.html"><img border="0" alt="[Top]" src="icons/top.gif"></a><a href="c-config.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="c-config2.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="84224">2.1 Introduction</a></i></h3></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="84225"> </a>This chapter introduces the configuration and use of the standard VxWorks network stack, the details of which are given in subsequent chapters.</p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H3"><i><a name="94334">2.1.1 The Data Link Layer</a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="94335"> </a>Chapter <a href="c-dll.html#94225"><i class="title">3. Data Link Layer Network Components</i></a> is a discussion of the data link layer, its general configuration needs, and network drivers. These drivers handle the specifics of communicating over networking hardware, such as an Ethernet board, a serial line, or even the shared-memory backplane. These drivers are the foundation of the network stack. For information on booting VxWorks using these drivers, see chapter <a href="c-booting.html#84222"><i class="title">13. Booting over the Network</i></a>.</p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H3"><i><a name="94165">2.1.2 The MUX, TCP/IP, and Associated Protocols</a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="94168"> </a>After the chapter on the data link layer, chapter <a href="c-tcpip.html#84223"><i class="title">4. TCP/IP Under VxWorks</i></a> introduces the MUX and the TCP/IP protocol suite. Under VxWorks, TCP/IP uses the MUX interface to communicate with the data link layer. The purpose of the MUX is to decouple the data link and network layers. This makes it easier to add new network drivers under an existing protocol. It also makes it easier for an alternative protocol to run over the standard VxWorks data link layer. For more information on the MUX, see the <i class="title">Network Protocol Toolkit User's Guide</i>.</p><dd><p class="Body"><a name="84238"> </a>The discussion of IP, TCP, and UDP is primarily an overview that prepares you for a discussion of their configuration needs under VxWorks. However, this chapter does describe ARP and Proxy ARP in some detail. ARP provides dynamic mapping from an IP address to the corresponding media address. Using ARP, VxWorks implements a proxy ARP scheme that can make distinct networks appear as one logical network. This proxy ARP scheme is an alternative to the use of explicit subnets for accessing the shared-memory network. </p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H3"><i><a name="84241">2.1.3 Network Configuration Protocols</a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="84242"> </a>The next group of protocols discussed, in chapter <a href="c-netconfig.html#84223"><i class="title">5. Network Configuration Protocols</i></a>, are the network configuration protocols:</p></dl><dl class="margin"><ul class="BulletSingle" type="disc"><li><a name="84244"> </a>DHCP, Dynamic Host Configuration Protocol</li></ul><ul class="BulletSingle" type="disc"><li><a name="84246"> </a>BOOTP, Bootstrap Protocol</li></ul><ul class="BulletSingle" type="disc"><li><a name="84247"> </a>SNMP, Simple Network Management Protocol</li></ul></dl><dl class="margin"><dd><p class="Body"><a name="84248"> </a>The networking stack can use either DHCP or BOOTP to set up and maintain its network configuration information. At boot time, both DHCP and BOOTP can provide IP addresses and related information. BOOTP assigns IP addresses permanently. The DHCP protocol extends BOOTP to allow the assignment of IP addresses on a temporary basis. Thus, the client receives an IP address on lease. When the lease expires, the client must renegotiate the lease. As a result, DHCP remains active during run-time. </p><dd><p class="Body"><a name="84249"> </a>Although SNMP can provide network configuration information, it differs significantly from BOOTP and DHCP in that it was not designed for use at boot time. Instead, you use it to set up network management station (NMS) from which you can remotely configure, monitor, and control network devices called <i class="term">agents</i>. Thus, SNMP is a network configuration protocol, but in a very different sense of the term. </p><dd><p class="Body"><a name="84250"> </a>Beyond providing a few paragraphs of description, this manual does not discuss SNMP. For detailed information on using SNMP with VxWorks, see <i class="title">WindNet SNMP VxWorks Optional Product Supplement. </i></p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H3"><i><a name="84252">2.1.4 <a href="c-network.html#106834">Routing Applications</a></a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="84253"> </a>Chapter <a href="c-drp.html#94280"><i class="title">6. Dynamic Routing Protocols</i></a> discusses the routing applications: </p></dl><dl class="margin"><ul class="BulletSingle" type="disc"><li><a name="84256"> </a><a href="c-network.html#106841">RIP, Routing Information Protocol </a></li></ul><dl class="margin"><dd><div class="Indent"><a name="84257"> </a>RIP maintains routing information within small inter-networks. The RIP server provided with VxWorks is based on the 4.4 BSD <b class="symbol_lc">routed</b> program. The VxWorks RIP server supports three modes of operation: Version 1 RIP, Version 2 RIP with multicasting, and Version 2 RIP with broadcasting. </div><br></dl><ul class="BulletSingle" type="disc"><li><a name="84260"> </a><a href="c-network.html#106838">OSPF, Open Shortest Path First</a></li></ul><dl class="margin"><dd><div class="Indent"><a name="84261"> </a>Like RIP, OSPF updates the information in the routing tables. However, OSPF is more complex than RIP. This complexity enhances functionality. Thus, an OSPF router can handle inter-networks that are too large for RIP. Unfortunately, this complexity also makes OSPF much harder to configure. </div><br></dl></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H3"><i><a name="84265">2.1.5 <a href="c-network.html#106835">Networking APIs</a></a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="84266"> </a>Chapter <a href="c-netapi.html#94280"><i class="title">7. Networking APIs</i></a> discusses the VxWorks implementation of sockets. Using sockets, applications can communicate across a backplane, within a single CPU, across an Ethernet, or across any connected combination of networks. Socket communications can occur between any combination of VxWorks tasks and host system processes. VxWorks supports a standard BSD socket interface to TCP and UDP. Using these standard BSD sockets, you can:</p></dl><dl class="margin"><ul class="BulletSingle" type="disc"><li><a name="84267"> </a>Communicate with other processes. </li></ul><ul class="BulletSingle" type="disc"><li><a name="94400"> </a>Access the IP multicasting functionality. </li></ul><ul class="BulletSingle" type="disc"><li><a name="94401"> </a>Review and modify the routing tables. </li></ul></dl><dl class="margin"><dd><p class="Body"><a name="94402"> </a>In addition to the standard BSD socket interface, VxWorks also supports zbuf sockets, an alternative set of socket calls based on a data abstraction called the zbuf (the zero-copy buffer). Using zbuf sockets, you share data buffers (or portions of data buffers) between separate software modules. Although this interface is WRS-specific, the interface can communicate with standard BSD sockets. Thus, the other end of the socket connection can use the standard BSD interface even if you chose to use the zbuf interface on the VxWorks side of the connection. </p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H3"><i><a name="84272">2.1.6 DNS, Domain Name System</a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="84274"> </a>DNS is a distributed database that most TCP/IP applications can use to translate host names to IP addresses and back. DNS uses a client/server architecture. The client side is known as the <i class="emphasis">resolver</i>. The server side is called the <i class="emphasis">name server</i>. VxWorks provides the resolver functionality in <b class="library">resolvLib</b>. DNS is discussed briefly in chapter <a href="c-dns.html#94280"><i class="title">8. DNS: Domain Name System</i></a>. For detailed information on DNS, see <i class="title">RFC-1034</i> and <i class="title">RFC-1035</i>. </p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H3"><i><a name="84277">2.1.7 SNTP, Simple Network Time Protocol</a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="84278"> </a>Using an SNTP client, a target can maintain the accuracy of its internal clock based on time values reported by one or more remote sources. Using an SNTP server, the target can provide time information to other systems. SNTP is discussed briefly in chapter <a href="c-sntp.html#94280"><i class="title">9. SNTP: A Time Protocol</i></a>.</p></dl></dl><font face="Helvetica, sans-serif" class="sans"><h4 class="H3"><i><a name="84279">2.1.8 Remote Access Applications</a></i></h4></font><dl class="margin"><dl class="margin"><dd><p class="Body"><a name="84281"> </a>Chapters <a href="c-rpc.html#94280"><i class="title">10. RPC: Remote Procedure Calls</i></a>, <a href="c-fileaxs.html#94280"><i class="title">11. File Access Applications</i></a>, and <a href="c-rlotln.html#94280"><i class="title">12. rlogin and telnet: Host Access Applications</i></a> discuss the applications that provide remote access over the network. VxWorks supports the following:</p></dl><dl class="margin"><ul class="BulletSingle" type="disc"><li><a name="84282"> </a>RPC (Remote Procedure Call, for distributed processing) </li></ul><ul class="BulletSingle" type="disc"><li><a name="84283"> </a>RSH (Remote Shell, for remote file access) </li></ul><ul class="BulletSingle" type="disc"><li><a name="84284"> </a>FTP (File Transfer Protocol, for remote file access) </li></ul><ul class="BulletSingle" type="disc"><li><a name="84285"> </a>NFS (Network File System, for remote file access) </li></ul><ul class="BulletSingle" type="disc"><li><a name="84286"> </a>TFTP (Trivial File Transfer Protocol, for remote file access) </li></ul><ul class="BulletSingle" type="disc"><li><a name="84287"> </a><b class="symbol_lc">rlogin</b> (for remote login) </li></ul><ul class="BulletSingle" type="disc"><li><a name="84288"> </a><b class="symbol_lc">telnet</b> (for remote login)</li></ul></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-config.html"><img border="0" alt="[Index]" src="icons/index.gif"></a><a href="c-config.html"><img border="0" alt="[Top]" src="icons/top.gif"></a><a href="c-config.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="c-config2.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 + -