mirror of
https://github.com/RIOT-OS/RIOT.git
synced 2024-12-29 04:50:03 +01:00
d2a3ff3d83
- renamed:
- `bluepill` --> `bluepill-stm32f103c8`
- `bluepill-128kib` --> `bluepill-stm32f103cb`
- `blackpill` --> `blackpill-stm32f103c8`
- `blackpill-128kib` --> `blackpill-stm32f103cb`
- doc:
- added link to corresponding hardware page on the STM32-base
project
- added picture
|
||
|---|---|---|
| .. | ||
| dtls-client.c | ||
| dtls-server.c | ||
| main.c | ||
| Makefile | ||
| Makefile.ci | ||
| README.md | ||
| tinydtls_common.h | ||
| tinydtls_keys.h | ||
DTLS sock async test application
This is a test application for DTLS sock sock_dtls_t with sock_async.
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 += -DCONFIG_DTLS_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.