-
Notifications
You must be signed in to change notification settings - Fork 424
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does the develop branch of libcoap support lwIP #3
Comments
Hi Fang Huaqi, Fang Huaqi notifications@github.com writes:
Last time I checked, the example worked, but I will look into this. (The Best regards |
OK, thanks a lot, once you have some update for this test, could you kindly let me know, thanks a lot. |
the development head is currently missing the i'm in the process of updating the lwip port to integrate better with the latest libcoap infrastructure and will update this bug when mergable fixes are available. |
I have added WITH_LWIP and checked that at least the build process works again. |
I want to know whether the POSIX means OS or stardard TCP/IP protocol? |
POSIX as in https://en.wikipedia.org/wiki/POSIX. libcoap supports standard IP as in RFC 2460 (and some support for legacy IP as of RFC 792, though). No TCP yet. |
Addresses issue with HKDF and HMAC usage by clearly setting out what is happening as TLS libraries only support HMAC.
Addresses issue with HKDF and HMAC usage by clearly setting out what is happening as TLS libraries only support HMAC.
Addresses issue with HKDF and HMAC usage by clearly setting out what is happening as TLS libraries only support HMAC.
Addresses issue with HKDF and HMAC usage by clearly setting out what is happening as TLS libraries only support HMAC.
Addresses issue with HKDF and HMAC usage by clearly setting out what is happening as TLS libraries only support HMAC.
Addresses issue with HKDF and HMAC usage by clearly setting out what is happening as TLS libraries only support HMAC.
Addresses issue with HKDF and HMAC usage by clearly setting out what is happening as TLS libraries only support HMAC.
Addresses issue with HKDF and HMAC usage by clearly setting out what is happening as TLS libraries only support HMAC.
Addresses issue with HKDF and HMAC usage by clearly setting out what is happening as TLS libraries only support HMAC.
Addresses issue with HKDF and HMAC usage by clearly setting out what is happening as TLS libraries only support HMAC.
Addresses issue with HKDF and HMAC usage by clearly setting out what is happening as TLS libraries only support HMAC.
Addresses issue with HKDF and HMAC usage by clearly setting out what is happening as TLS libraries only support HMAC.
Addresses issue with HKDF and HMAC usage by clearly setting out what is happening as TLS libraries only support HMAC.
Addresses issue with HKDF and HMAC usage by clearly setting out what is happening as TLS libraries only support HMAC.
I tried to clone the source code, and follow the get started guide, but it seems the lwip example can't be compiled successfully. So I am wondering if the lwip support is still under development?
The text was updated successfully, but these errors were encountered: