c-tcpip7.html

Vxworks网络编程指南

<p><ol class="List"><li value="3)"><a name="94655"> </a>Proxy ARP server (<b class="symbol_UC">INCLUDE_PROXY_SERVER</b>)</li></ol></p>
<p><ol class="List"><li value="4)"><a name="94656"> </a>Auto address setup (<b class="symbol_UC">INCLUDE_SM_SEQ_ADDR</b>) - required only for default addressing</li></ol></p>
<p><ol class="List"><li value="5)"><a name="94664"> </a>Default address for bp (<b class="symbol_UC">INCLUDE_PROXY_DEFAULT_ADDR</b>) - required only for default addressing</li></ol></p>
<dl class="margin">

<b class="BulletHead"><li><a name="94666"> </a><font face="Helvetica, sans-serif" size="-1" class="sans">Master Definition in <b class="file">config.h:</b></font></li></b>
<dl class="margin">

<dd><pre class="Code3"><b><a name="87989">#define PROXY_ARP_MASTER 
#define SM_OFF_BOARD=FALSE</a></b></pre>
</dl>

<b class="BulletHead"><li><a name="87991"> </a><font face="Helvetica, sans-serif" size="-1" class="sans">Slave definition in <b class="file">config.h:</b></font></li></b>
<dl class="margin">

<dd><pre class="Code3"><b><a name="87992">#define PROXY_ARP_SLAVE 
#define SM_OFF_BOARD=TRUE</a></b></pre>
</dl>

</dl>

</dl>

<dd><font face="Helvetica, sans-serif" size="-1" class="sans">
<h5 class="HU"><i><a name="87994">Setting Up Boot Parameters and Booting</a></i></h5>
</font><dl class="margin">

<dd><p class="Body"><a name="87998"> </a>See <a href="c-dll5.html#85549"><i class="title">3.5&nbsp;Shared-Memory Network on the Backplane</i></a> for information on booting shared memory networks. After booting <b class="symbol_lc">vx1</b> (the master), use <b class="routine"><i class="routine">smNetShow</i></b><b>(&nbsp;)</b> to find the shared memory anchor, which will be used with the slave boot device (for <b class="symbol_lc">vx2</b>, <b class="symbol_lc">vx3</b>, and <b class="symbol_lc">vx4</b>). You will need to run <b class="routine"><i class="routine">sysLocalToBusAddr</i></b><b>(&nbsp;)</b> on the master and <b class="routine"><i class="routine">sysBusToLocalAddr</i></b><b>(&nbsp;)</b> on each type of target to get the correct bus address for the anchor. For general information on boot parameters, see the <i class="title">Tornado User's Guide: Getting Started</i>.</p>
</dl>

<dd><font face="Helvetica, sans-serif" size="-1" class="sans">
<h5 class="HU"><i><a name="88002">Creating Network Connections</a></i></h5>
</font><dl class="margin">

<dd><b class="HU-run"><a name="88003"> </a><font face="Helvetica, sans-serif" size="-1" class="sans">From vx1 (the master):</font></b>
</dl>

<dl class="margin">

<dd><p class="Body"><a name="88005"> </a>Use <b class="routine"><i class="routine">routeAdd</i></b><b>(&nbsp;)</b> to tell the master (the proxy server) about the IP routing network by running the following:</p>
<dl class="margin">

<dd><pre class="Code2"><b><a name="88006"></b><tt class="output">-&gt;</tt><b> routeAdd ("161.27.0.0", "150.12.0.6") 
</b><tt class="output">value = 0 = 0x0</tt><b></a></b></pre>
</dl>

</dl>

<dl class="margin">

<dd><b class="HU-run"><a name="88008"> </a><font face="Helvetica, sans-serif" size="-1" class="sans">From vx3:</font></b>
</dl>

<dl class="margin">

<dd><p class="Body"><a name="88009"> </a>Since  <b class="symbol_lc">vx3</b> boots from the shared memory network,  it needs to have its connection to the IP routing network brought up explicitly.  The following example shows how to do this for <b class="symbol_lc">vx3</b> in <a href="c-tcpip7.html#87887">Figure&nbsp;4-16</a>:</p>
<dl class="margin">

<dd><pre class="Code2"><b><a name="88013"></b><tt class="output">-&gt;</tt><b> userNetIfAttach ("ln", "161.27.0.1") 
</b><tt class="output">Attaching network interface ln0...done. 
value = 0 = 0x0 
-&gt;</tt><b> userNetIfConfig ("ln", "161.27.0.1", "t0-1", 0xffffff00) 
</b><tt class="output">value = 0 = 0x</tt><b></a></b></pre>
</dl>

</dl>

</dl>

<dl class="margin">
<dd>
<p class="table" callout>
<table border="0" cellpadding="0" cellspacing="0">
<tr valign="top">
<td valign="top" width="40">
<br>
<img border="0" alt="*" src="icons/note.gif">
</td>

<td>
<hr><div class="CalloutCell"><a name="91952"><b class="symbol_UC"><font face="Helvetica, sans-serif" size="-1" class="sans">NOTE:  </font></b></a>Substitute the appropriate network boot device for <i class="textVariable">"ln"</i>.  The correct boot device is the first one given by <b class="routine"><i class="routine">ifShow</i></b><b>(&nbsp;)</b>. </div>
</td>


</tr>
<tr valign="top">
<td></td>

<td><hr></td>


</tr>

<tr valign="middle">
<td colspan="20">

</td>
</tr>
</table>
</p callout>



</dl>
<dl class="margin">

<dd><font face="Helvetica, sans-serif" size="-1" class="sans">
<h5 class="HU"><i><a name="88026">Diagnosing Shared Memory Booting Problems</a></i></h5>
</font><dl class="margin">

<dd><p class="Body"><a name="88030"> </a>See <a href="c-dll5.html#86132"><i class="title">Troubleshooting</i></a> for information on debugging the shared memory network.</p>
</dl>

<dd><font face="Helvetica, sans-serif" size="-1" class="sans">
<h5 class="HU"><i><a name="88031">Diagnosing Routing Problems</a></i></h5>
</font><dl class="margin">

<dd><p class="Body"><a name="88033"> </a>The following routines can be useful in locating the source of routing problems:</p>
</dl>

<dl class="margin">

<dd><div class="Item"><a name="88035"> </a><b class="routine"><i class="routine">ping</i></b><b>(&nbsp;)</b> </div>
<dl class="margin">

<dd><div class="Indent"><a name="88036"> </a>Starting from <b class="symbol_lc">vx1</b>, ping other processors in turn to see if you get the expected result. The function returns <b class="symbol_UC">OK</b> if it reaches the other machine, or <b class="symbol_UC">ERROR</b> if the connection fails.</div>
<br>
</dl>

<dd><div class="Item"><a name="88038"> </a><b class="routine"><i class="routine">smNetShow</i></b><b>(&nbsp;)</b></div>
<dl class="margin">

<dd><div class="Indent"><a name="88039"> </a>This routine  displays cumulative activity statistics for all attached processors.</div>
<br>
</dl>

<dd><div class="Item"><a name="88041"> </a><b class="routine"><i class="routine">arpShow</i></b><b>(&nbsp;)</b></div>
<dl class="margin">

<dd><div class="Indent"><a name="88042"> </a>This routine displays the current Internet-to-Ethernet address mappings in the system ARP table.</div>
<br>
</dl>

<dd><div class="Item"><a name="88044"> </a><b class="routine"><i class="routine">arptabShow</i></b><b>(&nbsp;)</b></div>
<dl class="margin">

<dd><div class="Indent"><a name="88045"> </a>This routine displays the known Internet-to-Ethernet address mappings in the ARP table</div>
<br>
</dl>

<dd><div class="Item"><a name="88047"> </a><b class="routine"><i class="routine">routeShow</i></b><b>(&nbsp;)</b></div>
<dl class="margin">

<dd><div class="Indent"><a name="88048"> </a>This routine displays the current routing information contained in the routing table.</div>
<br>
</dl>

<dd><div class="Item"><a name="88050"> </a><b class="routine"><i class="routine">ifShow</i></b><b>(&nbsp;)</b></div>
<dl class="margin">

<dd><div class="Indent"><a name="88051"> </a>This routine displays the attached network interfaces for debugging and diagnostic purposes.</div>
<br>
</dl>

<dd><div class="Item"><a name="88053"> </a><b class="routine"><i class="routine">proxyNetShow</i></b><b>(&nbsp;)</b></div>
<dl class="margin">

<dd><div class="Indent"><a name="88054"> </a>This routine displays the proxy networks and their associated clients.</div>
<br>
</dl>

<dd><div class="Item"><a name="88056"> </a><b class="routine"><i class="routine">proxyPortShow</i></b><b>(&nbsp;)</b></div>
<dl class="margin">

<dd><div class="Indent"><a name="88058"> </a>This routine displays the ports currently enabled.</div>
<br>
</dl>

</dl>

</dl>


<a name="foot"><hr></a>

<p class="FootnoteNumberMarker">1:&nbsp;
<span class="Footnote"><a name="87234"> </a>Proxy ARP is described in Request For Comments (RFC) 925 "Multi LAN Address Resolution," and an implementation is discussed in RFC 1027 "Using ARP to Implement Transparent Subnet Gateways." The ARP protocol is described in RFC 826 "Ethernet Address Resolution Protocol: Or converting network protocol addresses to 48-bit Ethernet address for transmission on Ethernet hardware." The implementation of Proxy ARP for VxWorks is based on RFC 925. However, it is a limited subset of that proposal.</span>

<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-tcpip6.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="c-netconfig.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 --->