summaryrefslogtreecommitdiffstats
path: root/networking/testing_the_driver.rst
diff options
context:
space:
mode:
authorAmar Takhar <amar@rtems.org>2016-01-18 00:37:40 -0500
committerAmar Takhar <verm@darkbeer.org>2016-05-02 20:51:24 -0400
commitd389819eea3a84e388935153e3be847342809da3 (patch)
tree15cfe55f41281cead805ce87f66c5d7248caa9ce /networking/testing_the_driver.rst
parent11e1a6f969dc0b255dd7aed12509484cf7c7ed60 (diff)
downloadrtems-docs-d389819eea3a84e388935153e3be847342809da3.tar.bz2
Convert all Unicode to ASCII(128)
Diffstat (limited to 'networking/testing_the_driver.rst')
-rw-r--r--networking/testing_the_driver.rst44
1 files changed, 22 insertions, 22 deletions
diff --git a/networking/testing_the_driver.rst b/networking/testing_the_driver.rst
index d71747f..9a064e7 100644
--- a/networking/testing_the_driver.rst
+++ b/networking/testing_the_driver.rst
@@ -11,7 +11,7 @@ The network used to test the driver should include at least:
the operation of the target machine.
- An Ethernet network analyzer or a workstation with an
- ‘Ethernet snoop’ program such as ``ethersnoop`` or``tcpdump``.
+ 'Ethernet snoop' program such as ``ethersnoop`` or``tcpdump``.
- A workstation.
@@ -39,7 +39,7 @@ is a list of them:
- mbuf activity
There are commented out calls to ``printf`` in the file``sys/mbuf.h`` in the network stack code. Uncommenting
- these lines results in output when mbuf’s are allocated
+ these lines results in output when mbuf's are allocated
and freed. This is very useful for finding memory leaks.
- TX and RX queuing
@@ -91,29 +91,29 @@ is a list of them:
URL: (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-routing.html)
For a quick reference to the flags, see the table below:
- ‘``U``’
+ '``U``'
Up: The route is active.
- ‘``H``’
+ '``H``'
Host: The route destination is a single host.
- ‘``G``’
+ '``G``'
Gateway: Send anything for this destination on to this remote system, which
will figure out from there where to send it.
- ‘``S``’
+ '``S``'
Static: This route was configured manually, not automatically generated by the
system.
- ‘``C``’
+ '``C``'
Clone: Generates a new route based upon this route for machines we connect
to. This type of route is normally used for local networks.
- ‘``W``’
+ '``W``'
WasCloned: Indicated a route that was auto-configured based upon a local area
network (Clone) route.
- ‘``L``’
+ '``L``'
Link: Route involves references to Ethernet hardware.
- ``mbuf``
@@ -182,29 +182,29 @@ The network demonstration program ``netdemo`` may be used for these tests.
broadcast packets disabled:
Verify that the program continues to run once the driver has been attached.
-- Issue a ‘``u``’ command to send UDP
- packets to the ‘discard’ port.
+- Issue a '``u``' command to send UDP
+ packets to the 'discard' port.
Verify that the packets appear on the network.
-- Issue a ‘``s``’ command to print the network and driver statistics.
+- Issue a '``s``' command to print the network and driver statistics.
- On a workstation, add a static route to the target system.
-- On that same workstation try to ‘ping’ the target system.
+- On that same workstation try to 'ping' the target system.
Verify that the ICMP echo request and reply packets appear on the net.
- Remove the static route to the target system.
Modify ``networkconfig.h`` to attach the driver
with reception of broadcast packets enabled.
- Try to ‘ping’ the target system again.
+ Try to 'ping' the target system again.
Verify that ARP request/reply and ICMP echo request/reply packets appear
on the net.
-- Issue a ‘``t``’ command to send TCP
- packets to the ‘discard’ port.
+- Issue a '``t``' command to send TCP
+ packets to the 'discard' port.
Verify that the packets appear on the network.
-- Issue a ‘``s``’ command to print the network and driver statistics.
+- Issue a '``s``' command to print the network and driver statistics.
- Verify that you can telnet to ports 24742
and 24743 on the target system from one or more
@@ -232,7 +232,7 @@ Giant packets
- Recompile the driver with ``MAXIMUM_FRAME_SIZE`` set to
a smaller value, say 514.
-- ‘Ping’ the driver from another workstation and verify
+- 'Ping' the driver from another workstation and verify
that frames larger than 514 bytes are correctly rejected.
- Recompile the driver with ``MAXIMUM_FRAME_SIZE`` restored to 1518.
@@ -248,8 +248,8 @@ Resource Exhaustion
- Verify that the program operates properly and that you can
still telnet to both the ports.
-- Display the driver statistics (Console ‘``s``’ command or telnet
- ‘control-G’ character) and verify that:
+- Display the driver statistics (Console '``s``' command or telnet
+ 'control-G' character) and verify that:
# The number of transmit interrupts is non-zero.
This indicates that all transmit descriptors have been in use at some time.
@@ -262,7 +262,7 @@ Cable Faults
- Run the ``netdemo`` program.
-- Issue a ‘``u``’ console command to make the target machine transmit
+- Issue a '``u``' console command to make the target machine transmit
a bunch of UDP packets.
- While the packets are being transmitted, disconnect and reconnect the
@@ -277,7 +277,7 @@ Throughput
----------
Run the ``ttcp`` network benchmark program.
-Transfer large amounts of data (100’s of megabytes) to and from the target
+Transfer large amounts of data (100's of megabytes) to and from the target
system.
The procedure for testing throughput from a host to an RTEMS target