obgm/libcoap

0 Fork 0

mirror of https://github.com/obgm/libcoap.git synced 2026-11-08 02:22:54 +03:00

Files

T

Jon Shallow e25cf94d2a RIOT: Update to use SOCK i/f, not Posix

Remove all references to Posix functions, using Sock functions as appropriate.

Update coap_address_t to be RIOT specific when doing RIOT builds.

2024-03-12 17:15:01 +00:00

app.config

RIOT: library fixes for different build types

2023-10-23 14:38:57 +01:00

client-coap.c

RIOT: Update to use SOCK i/f, not Posix

2024-03-12 17:15:01 +00:00

client-coap.h

RIOT: Update to use SOCK i/f, not Posix

2024-03-12 17:15:01 +00:00

Kconfig

RIOT: library fixes for different build types

2023-10-23 14:38:57 +01:00

main.c

RIOT: library fixes for different build types

2023-10-23 14:38:57 +01:00

Makefile

RIOT: Update to use SOCK i/f, not Posix

2024-03-12 17:15:01 +00:00

Makefile.ci

RIOT: library fixes for different build types

2023-10-23 14:38:57 +01:00

README.md

RIOT: Update PKG_URL and PKG_VERSION to latest 4.3.2rc2 code

2023-08-14 10:43:28 +01:00

README.md

libcoap client example

This example shows how to configure a client to use libcoap

Fast configuration (Between RIOT instances):

Preparing the logical interfaces:

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

Client invocation

For the client:

PORT=tap0 make term
coapc coap://[ip6-address]/some/path

The IP address to connect to needs to be that as returned by libcoap_server, or that of the tap0 interface, etc.

Handling the static memory allocation

libcoap for RIOT is using the sys/memarray module and therefore there are certain limits. Said resources are defined in libcoap/src/coap_mem.c, but can be overwritten at compile time.