RIOT-OS/RIOT
RIOT-OS/RIOT
1
0
Fork 0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
Code Releases Activity
633aa8cd41
RIOT/examples/dtls-sock
History
Jean Pierre Dudey 633aa8cd41
boards: add cc1312-launchpad board. 
This is mostly based on the cc1352-launchpad boards, is essentially the same
buttons and leds pins, what changes is the CCXML files used to flash with
`make flash` and the UART pins.

Signed-off-by: Jean Pierre Dudey <jeandudey@hotmail.com>
2020-01-19 11:36:31 -05:00
..
dtls-client.c examples: add DTLS sock example application 2019-12-05 14:08:54 +01:00
dtls-server.c dtls-sock: check msg_try_receive return value 2019-12-09 14:17:09 +01:00
main.c examples: add DTLS sock example application 2019-12-05 14:08:54 +01:00
Makefile examples: add DTLS sock example application 2019-12-05 14:08:54 +01:00
Makefile.ci boards: add cc1312-launchpad board. 2020-01-19 11:36:31 -05:00
README.md examples: add DTLS sock example application 2019-12-05 14:08:54 +01:00
tinydtls_keys.h examples: add DTLS sock example application 2019-12-05 14:08:54 +01:00

README.md

DTLS sock example

This example shows how to use DTLS sock sock_dtls_t.

Testing using RIOT native

For testing, we can use two RIOT native RIOT instances. For that first we need to prepare the network interfaces:

$ ./../../dist/tools/tapsetup/tapsetup --create 2

For the server instance:

$ PORT=tap0 make all term
[...]
> dtlss start
ifconfig

For the client:

$ PORT=tap1 make all term
[...]
> dtlsc <server ip address> "DATA to send"

Debug logs

To enable debug logs uncomment CFLAGS += -DDTLS_DEBUG in the Makefile. Tinydtls supports setting the log level. See Makefile for more info.

Configs and constraints

DTLS sock acts as a wrapper for the underlying DTLS stack and as such, the constraints that applies specifically to the stack are also applied here. For tinydtls, please refer to dtls-echo README.