1c87c5fbaSopenharmony_ci# libcoap client example 2c87c5fbaSopenharmony_ci 3c87c5fbaSopenharmony_ciThis example shows how to configure a client to use libcoap 4c87c5fbaSopenharmony_ci 5c87c5fbaSopenharmony_ci## Fast configuration (Between RIOT instances): 6c87c5fbaSopenharmony_ci 7c87c5fbaSopenharmony_ciPreparing the logical interfaces: 8c87c5fbaSopenharmony_ci 9c87c5fbaSopenharmony_ci sudo ./../../dist/tools/tapsetup/tapsetup --create 2 10c87c5fbaSopenharmony_ci 11c87c5fbaSopenharmony_ci## Client invocation 12c87c5fbaSopenharmony_ciFor the client: 13c87c5fbaSopenharmony_ci 14c87c5fbaSopenharmony_ci PORT=tap0 make term 15c87c5fbaSopenharmony_ci coapc coap://[ip6-address]/some/path 16c87c5fbaSopenharmony_ci 17c87c5fbaSopenharmony_ciThe IP address to connect to needs to be that as returned by libcoap_server, 18c87c5fbaSopenharmony_cior that of the tap0 interface, etc. 19c87c5fbaSopenharmony_ci 20c87c5fbaSopenharmony_ci## Handling the static memory allocation 21c87c5fbaSopenharmony_ci 22c87c5fbaSopenharmony_cilibcoap for RIOT is using the `sys/memarray` module and therefore there 23c87c5fbaSopenharmony_ciare certain limits. Said resources are defined in `libcoap/src/coap_mem.c`, 24c87c5fbaSopenharmony_cibut can be overwritten at compile time. 25