zephyr/samples/net
Vinicius Costa Gomes fcf98d1534 samples/zoap_server: Add preliminary support for validation
Implement resources so they conform to what the ETSI plugtest suite
expects.

This allows the zoap-server sample to pass most of the tests of the
CORE[1] group, only TD_COAP_CORE_09 is not implemented.

Tests involving lossy networks weren't run as well.

The tests were run against the libcoap[2] client.

[1] ETSI CoAP test description
http://www.etsi.org/plugtests/CoAP/Document/CoAP_TestDescriptions_v015.pdf

[2] libcoap
https://libcoap.net/

Change-Id: Ifa3ed21a93052e02f47e99d7cb6d9d4b28e576d8
Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
2016-10-17 02:12:12 +00:00
..
coap_observe_client Revert "misc: Remove generic PRINT macros from net samples" 2016-08-23 13:19:44 -07:00
coap_server Revert "misc: Remove generic PRINT macros from net samples" 2016-08-23 13:19:44 -07:00
common net: samples: Fix RFC3849 address config option. 2016-08-10 15:14:44 +00:00
dhcp_client Revert "misc: Remove generic PRINT macros from net samples" 2016-08-23 13:19:44 -07:00
dns_client dns: Remove deprecated functionality 2016-09-12 02:15:44 +00:00
dtls_client Revert "misc: Remove generic PRINT macros from net samples" 2016-08-23 13:19:44 -07:00
dtls_server Revert "misc: Remove generic PRINT macros from net samples" 2016-08-23 13:19:44 -07:00
echo_client Revert "misc: Remove generic PRINT macros from net samples" 2016-08-23 13:19:44 -07:00
echo_server Revert "misc: Remove generic PRINT macros from net samples" 2016-08-23 13:19:44 -07:00
loopback_test Revert "misc: Remove generic PRINT macros from net samples" 2016-08-23 13:19:44 -07:00
mbedtls_sslclient samples/net: Remove call to unref routine when net_send returns >= 0 2016-08-18 16:08:11 +00:00
nats_clients samples/net: Add KNOWN_ISSUES file for NATS and DNS sample apps 2016-08-24 23:36:45 +00:00
paho_mqtt_clients mqtt: Add KNOWN_ISSUES file 2016-08-18 23:56:05 -05:00
test/test_15_4
test_15_4 boards: remove obsolete board basic_minuteia 2016-09-22 22:09:34 +00:00
trickle-legacy net: apps: Example app for Trickle algorithm 2016-09-12 02:00:12 +00:00
zoap_client samples/zoap-client: Add a README.txt to zoap-client 2016-10-01 01:11:27 +00:00
zoap_server samples/zoap_server: Add preliminary support for validation 2016-10-17 02:12:12 +00:00
zperf zperf_shell: add unified kernel string for unified kernel case 2016-09-13 17:12:55 -04:00
README samples/net: Add a sample for a CoAP client 2016-09-12 12:25:25 +00: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.


zoap_server
-----------

The Zoap server application implements a trivial CoAP server
which exposes a single resource "a/light", that only provides the
GET method.

It can be run similar to the echo_server sample: using two terminals,
(1) for zoap_server, run 'make server' in its directory, (2) for
zoap_client, run 'make client' in the zoap_client test directory.


zoap_client
-----------

The Zoap client application does a single request against a 'a/light'
resource, which has the first response lost (so retransmissions are
basically verified).

Please refer to the section above about how to run these applications
together.