Jon Shallow

I do not know the device, but if it is using CoAP over TLS (the article refers to TCP), you need to build a client with OpenSSL or GnuTLS support...

Not knowing the product, I cannot help you any more. If `coap-client coaps+tcp://.well-known/core` works (i.e it is a device running coaps as the protocol over tcp), then that will tell...

There are several things at play here. With this `libcoap-3.pc` fix and `cmake -DBUILD_SHARED_LIBS=ON` , everything works as expected for `libcoap-minimal`. Then for `autoconf `with `./configure --disable-shared`, `libcoap-minimal ` builds...

libcoap LwIP support has been re-written in PR https://github.com/obgm/libcoap/pull/884, and so this should no longer be an issue.

Closed as fixed in #926 which is now in the develop branch.

With CON requests, there is a RFC 7252 requirement that only one request can be active waiting for a response (NSTART is 1). If you want to send off all...

libcoap LwIP support has been re-written in PR https://github.com/obgm/libcoap/pull/884, and so this should no longer be an issue. The required header files are now in build type specific files.

Closed as fixed in #926 which is now in the develop branch.

libcoap LwIP support has been re-written in PR https://github.com/obgm/libcoap/pull/884, and so this should no longer be an issue.

I have no simple suggestions. I did think of memstream as an alternative to read from instead of a socket, but that always provides a null terminator.