Hi Robert,

Welcome to the wolfSSL Forums.

That is strange. Could you share the user_settings.h that reproduces this? Which version of wolfSSL are you building?

It might be easier to open a support ticket by emailing support@wolfssl.com

Kind regards,
Eric - wolfSSL Support

Hello Mika,

Welcome to the wolfSSL Forums.

wolfSSL has native support for LwIP, so you do not need to set up the IO callbacks. I think that is where your issue is coming from. We actually have an excellent LwIP example that you'll find useful:
https://github.com/wolfSSL/wolfssl-exam … aster/lwip

For LwIP native tcp sockets, define `WOLFSSL_LWIP_NATIVE`
For LwIP sockets API, just use `WOLFSSL_LWIP`

Could you tell us a bit about your project using wolfSSL and where you are from for our support records?

Kind regards,
Eric - wolfSSL Support

Hello mallenbach,

Welcome to the wolfSSL Forums!

Thanks for reaching out. Could you tell us a bit about your wolfBoot project and where you are located for our support statistics?

I am looping in a colleague to help with your question.

Kind regards,
Eric - wolfSSL Support

Hi Alice,

Thanks for contacting wolfSSL Support. Are you publishing from multiple threads? If so you'll need to enable mutex support with the multithread config option
--enable-mt (or define WOLFMQTT_MULTITHREAD)

Could you share the full configuration?

It might be easier for you to submit a support ticket by emailing support@wolfssl.com

Thanks,
Eric

Hello krcenov,

Welcome to the wolfSSL Forums!

I see you are specifying `-DWOLFSSL_USER_SETTINGS` in the CFLAGS. But you are also adding settings using ./configure. These could be conflicting. We recommend using either the `user_settings.h` header, or `./configure` and generating the options.h header.

Are you including the settings header before any other wolfSSL includes?

Check out our examples repository:
https://github.com/wolfSSL/wolfssl-examples

Specifically:
https://github.com/wolfSSL/wolfssl-exam … callback.c

Can you tell us a bit about yourself and the project you are working on for our support records? Feel free to send an email to support@wolfssl.com for a more private correspondence.

Thanks,
Eric - wolfSSL Support

Hi Sunny,

Cert creation form Dilthium keys is not currently supported in wolfCLU. We are working on some PQC cert functionality in wolfCLU. If you'd like to get this specific functionality developed, please send an email to support@wolfssl.com to make a formal feature request.

Thanks,
Eric

Please try adding a define for `WOLFSSL_WC_DILITHIUM`

Hi Ajith,

Is this related to a commercial effort which you have a support contract? If so, please send an email to support@wolfssl.com to open a proper support request.

Thanks,
Eric - wolfSSL Support

Hi Bryce,

Please send an email to support@wolfssl.com

This forum is not our preferred communication channel for customers.

Thanks,
Eric

Hi Jay,

Welcome to the wolfSSL Forums! Could you tell us a bit about your project using wolfMQTT?

I'd recommend starting with building the mqttclient example in VS. We did not create a VS project for the mqttsimple example.

The project settings for the example need to have the right pre-proccessor macros and include path set up. You can review the existing example projects to see the required settings.

Thanks,
Eric - wolfSSL Support

Hi harlansisson745

Oftentimes this is a result of an invalid configuration or an include path issue. The OpenSSL compatibility layer API is enabled with

#define OPENSSL_EXTRA
#define OPENSSL_ALL

Can you let us know what version of wolfSSL you are using and the full configuration?

Can you tell us a bit about your project and where you are located for our support records?

Thanks,
Eric - wolfSSL Support

That's the gist of it. Basically enable crypto dev support, then call the the crypto operation with the device ID. Here are some more examples using the CAAM:
https://github.com/wolfSSL/wolfssl-exam … /caam/seco