zephyr/samples/net
Jukka Rissanen 5f3f331d48 net: Adapt to new behavior of net_buf_frag_add v2
This change is related to patch called
"net: Adapt to new behavior of net_buf_frag_add"

This version removes extra net_nbuf_unref() from
the code. The unref was done because net_buf_frag_del()
did not remove the double ref from the list element.

Because of the other patch, the list does not have
double ref any more, so we need to remove the extra
unref in couple of extra places.

Change-Id: If90e01c24b9b4e68afbfa283850d2a1ecb3065ed
Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2016-12-02 12:40:54 +02:00
..
coap_observe_client
coap_server
common samples: net: Qemu make utilities update 2016-12-02 12:40:24 +02:00
dhcp_client
dhcpv4_client net: apps: Add DHCPv4 client sample application 2016-12-02 12:40:26 +02:00
dns_client iot/dns: Update README files 2016-12-02 12:40:52 +02:00
dtls_client
dtls_server
echo_client net: Rename net_nbuf_write to net_nbuf_append 2016-12-02 12:40:51 +02:00
echo_server net: Adapt to new behavior of net_buf_frag_add v2 2016-12-02 12:40:54 +02:00
ieee802154 samples: quark_se_devboard has been renamed to quark_se_c1000_devboard 2016-12-02 12:40:27 +02:00
loopback_test
mbedtls_dtlsclient net: Rename net_nbuf_write to net_nbuf_append 2016-12-02 12:40:51 +02:00
mbedtls_sslclient
nats_clients
paho_mqtt_clients
test/test_15_4
test_15_4
trickle-legacy
wpan_serial wpan_serial: Implement 802.15.4 serial radio protocol 2016-12-02 12:40:52 +02:00
wpanusb wpanusb: Add wpanusb syslog domain 2016-12-02 12:40:54 +02:00
zoap_client samples/zoap_client: Use token generator helper 2016-12-02 12:40:50 +02:00
zoap_server iot/zoap: Port to the native stack 2016-12-02 12:40:50 +02:00
zperf
README net: samples: Add samples overview for wpanusb and wpan_serial 2016-12-02 12:40:54 +02: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-tools project README file [1]. 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-tools project README file [1]. 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.

wpanusb
-------

The wpanusb application exports IEEE 802.15.4 radio over USB to be used in
other Operating Systems like Linux. In this scenario Linux SoftMAC driver
must be used implementing IEEE 802.15.4 stack inside Linux.

wpan_serial
-----------

The wpan_serial application implements IEEE 802.15.4 "serial-radio" protocol.
This is the protocol used in Contiki-based native border routers.

[1] https://gerrit.zephyrproject.org/r/gitweb?p=net-tools.git;a=summary