Skip to content

Latest commit

 

History

History
97 lines (65 loc) · 2.02 KB

README.md

File metadata and controls

97 lines (65 loc) · 2.02 KB
Raw

Posix sockets: TLS client/server example

This example shows how to use wolfSSL TLS sockets over RIOT-OS POSIX sockets

License

This example is distributed under the terms of GNU GPLv2.

SOCK vs. Socket

This example is configured to use wolfSSL on RIOT-OS over POSIX sockets (LWIP).

Fast configuration (Between RIOT instances)

Prepare the bridge interface linking two tuntap

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

Testing

Prerequisite

Ensure that the following are installed in your system:

  • gcc-multilib
  • bridge-utils

Clone RIOT-OS in a directory on your filesystem.

Run the server

$ make all RIOTBASE=/path/to/riot-os; PORT=tap1 make term
> tlss

Run the client

The default IP address assigned to all nodes is 192.168.7.2.

In order to run two nodes, you must modify the default address in main.c and re-compile the client application after starting the server.

$ PORT=tap0 make term
> tlsc <server address>

Note: You must be root to run make term, or else your user must have permissions to access /dev/net/tun.

Testing against host endpoints

Riot-to-host can be tested against wolfSSL client/server. The default IP address assigned to the RIOT node in native mode is "192.168.7.2".

Testing TLS server on node

$ make term

From another console, assign address to the tap0 device on the host:

$ ifconfig tap0 192.168.7.1/24 up

From the RIOT native node, start the server:

> tlss

On the host, connect using wolfSSL example client

$ wolfssl/examples/client/client -h 192.168.7.2

Testing TLS client on node

$ make term

From another console, assign address to the tap0 device on the host:

$ ifconfig tap0 192.168.7.1/24 up

Start the wolfSSL example server (-b is to listen on all interfaces, -d disables client certificate verification)

$ wolfssl/examples/server/server -b -d

From the RIOT native node, start the client:

> tlsc 192.168.7.1