zephyr/samples/net
jgarcia 7b8d89d921 net:apps: zperf application
zperf is a network traffic generator for Zephyr.
Same application is able to work dynamically in client or server mode.
It allows to assess network bandwidth.
zperf is compliant with iperf_2.0.5.
zperf can be run in micro or nano kernel.

Change-Id: Icbd69e1ad56ad29c678b098e7a2e07c44f90e48e
Signed-off-by: jgarcia <jeremie.garcia@intel.com>
2016-04-18 06:07:02 +00:00
..
coap_observe_client net: apps: Move Makefile.ipstack to common folder 2016-03-16 11:40:17 +00:00
coap_server net: apps: Move Makefile.ipstack to common folder 2016-03-16 11:40:17 +00:00
common net: apps: Move Makefile.ipstack to common folder 2016-03-16 11:40:17 +00:00
dtls_client net: apps: Move Makefile.ipstack to common folder 2016-03-16 11:40:17 +00:00
dtls_server net: apps: Move Makefile.ipstack to common folder 2016-03-16 11:40:17 +00:00
echo_client net: Test random is necessary to use CC2520 as radio driver 2016-04-14 07:49:22 +00:00
echo_server net: apps: Move Makefile.ipstack to common folder 2016-03-16 11:40:17 +00:00
loopback_test net: apps: User can set the loopback test count 2016-03-14 12:45:07 +00:00
test/test_15_4 Use BOARD instead of PLATFORM_CONFIG 2016-02-05 20:25:11 -05:00
test_15_4 net: apps: Move net samples to one directory instead of per kernel 2016-02-11 13:08:44 -05:00
zperf net:apps: zperf application 2016-04-18 06:07:02 +00:00
README net: Rename samples/network to samples/net 2016-02-05 20:24:39 -05:00

README

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.