1 <!-- Copyright (C) 2003 Red Hat, Inc. -->
2 <!-- This material may be distributed only subject to the terms -->
3 <!-- and conditions set forth in the Open Publication License, v1.0 -->
4 <!-- or later (the latest version is presently available at -->
5 <!-- http://www.opencontent.org/openpub/). -->
6 <!-- Distribution of the work or derivative of the work in any -->
7 <!-- standard (paper) book form is prohibited unless prior -->
8 <!-- permission is obtained from the copyright holder. -->
12 >Standalone Tests</TITLE
13 ><meta name="MSSmartTagsPreventParsing" content="TRUE">
16 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
19 TITLE="eCos Reference Manual"
20 HREF="ecos-ref.html"><LINK
22 TITLE="Tests and Demonstrations"
23 HREF="net-common-tests-and-demonstrations.html"><LINK
25 TITLE="Building the Network Tests"
26 HREF="net-common-building-the-network-tests.html"><LINK
28 TITLE="Performance Test"
29 HREF="net-common-performance-test.html"></HEAD
40 SUMMARY="Header navigation table"
49 >eCos Reference Manual</TH
57 HREF="net-common-building-the-network-tests.html"
65 >Chapter 36. Tests and Demonstrations</TD
71 HREF="net-common-performance-test.html"
85 NAME="NET-COMMON-STANDALONE-TESTS">Standalone Tests</H1
93 CLASS="PROGRAMLISTING"
100 > - trivial test of socket creation API
107 > - trivial test of mbuf allocation API</PRE
112 >These two do not communicate over the net; they just perform
113 simple API tests then exit.</P
121 CLASS="PROGRAMLISTING"
128 > - simple FTP test, connects to “server”</PRE
133 >This test initializes the interface(s) then connects to the
134 FTP server on the “server” machine for for each
135 active interface in turn, confirms that the connection was successful,
136 disconnects and exits. This tests interworking with the server.</P
144 CLASS="PROGRAMLISTING"
151 > - pings “server” and non-existent host to test timeout</PRE
156 >This test initializes the interface(s) then pings the server
157 machine in the standard way, then pings address “32 up” from
158 the server in the expectation that there is no machine there. This
159 confirms that the successful ping is not a false positive, and tests
160 the receive timeout. If there is such a machine, of course the
161 2nd set of pings succeeds, confirming that we can talk to a machine
162 not previously mentioned by configuration or by bootp. It then does
163 the same thing on the other interface, eth1.</P
171 CLASS="PROGRAMLISTING"
178 > - ping test, but also manipulates DHCP leases</PRE
183 >This test is very similar to the ping test, but in addition,
184 provided the network package is not configured to do this automatically,
185 it manually relinquishes and reclaims DHCP leases for all available
186 interfaces. This tests the external API to DHCP. See section below
195 CLASS="PROGRAMLISTING"
202 > - a flood ping test; use with care</PRE
207 >This test performs pings on all interfaces as quickly as possible,
208 and only prints status information periodically. Flood pinging is
209 bad for network performance; so do not use this test on general
210 purpose networks unless protected by a switch.</P
217 SUMMARY="Footer navigation table"
228 HREF="net-common-building-the-network-tests.html"
246 HREF="net-common-performance-test.html"
256 >Building the Network Tests</TD
262 HREF="net-common-tests-and-demonstrations.html"
270 >Performance Test</TD