zephyr/samples/network
Anas Nashif 36579879c2 use zephyr.h instead of microkernel/nanokernel.h
Cleanup header inclusion and only include zephyr.h in samples
and applications.

Change-Id: If7460f4c6305a1c1cfcfdcf6a9bb7423f410c5c6
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-02-05 20:24:35 -05:00
..
coap_observe_client use zephyr.h instead of microkernel/nanokernel.h 2016-02-05 20:24:35 -05:00
coap_server use zephyr.h instead of microkernel/nanokernel.h 2016-02-05 20:24:35 -05:00
dtls_client use zephyr.h instead of microkernel/nanokernel.h 2016-02-05 20:24:35 -05:00
dtls_server use zephyr.h instead of microkernel/nanokernel.h 2016-02-05 20:24:35 -05:00
echo_client use zephyr.h instead of microkernel/nanokernel.h 2016-02-05 20:24:35 -05:00
echo_server use zephyr.h instead of microkernel/nanokernel.h 2016-02-05 20:24:35 -05:00
listener use zephyr.h instead of microkernel/nanokernel.h 2016-02-05 20:24:35 -05:00
loopback_test use zephyr.h instead of microkernel/nanokernel.h 2016-02-05 20:24:35 -05:00
test_15_4 use zephyr.h instead of microkernel/nanokernel.h 2016-02-05 20:24:35 -05:00
README net: apps: Add readme file describing various IP stack examples 2016-02-05 20:24:25 -05:00

Description of various IP stack test applications
=================================================

echo_server
-----------

The echo server test implements a network server that listens
UDP sockets. If that socket receives data, the server reverses
the data and sends it back.

The echo client can be running in the host system in which
case you need to use SLIP to connect to qemu. This usage scenario
is described in net/ip/tools/README file. This is the default
if you type "make qemu" in echo_server test application directory.
The network IP stack hooks right under IP stack (network level)
and sends the IP packet to host using SLIP. The layer 2 is the
SLIP layer in this case, no radio layer is simulated or used.

The echo server qemu instance can also be running against echo
client that is running in another qemu. For this you need two
terminal windows. In terminal 1 go to echo_server directory
and type "make server". This will start the echo server and setup
qemu pipes in suitable way and it will also start monitor application
that will store the transferred network traffic into pcap file
for later analysis. Then in terminal 2 go to echo_client directory and
type "make client". This will start the echo client that will
start to send data to the server and verify that it has received
the data back correctly. In the two qemu case we are simulating
the whole radio network meaning that the saved pcap file will
contain 802.15.4 network packets.


echo_client
-----------

The echo client test implements a network client that will
send UDP data to the echo server. The client verifies that
it has received data to the sent message and that the data
is correct.

The echo server can be running in the host system in which case
you need to use SLIP to connect to qemu. This usage scenario
is described in net/ip/tools/README file. This is the default
if you type "make qemu" in echo_client test application directory.
The network IP stack hooks right under IP stack (network level)
and sends the IP packet to host using SLIP. The layer 2 is the
SLIP layer in this case, no radio layer is simulated or used.

The echo client qemu instance can also be running against echo
server that is running in another qemu. This test scenario is
described in echo_server chapter above.