Hi there,

i like to use the wolfssl lib for encyrption on my stm32f4 i aalso want to use the raw lwip from the stm32cube.
I was able to set it up as described in the "Lwip native #599" post. I got it to work but i get error debug prints.

wolfSSL Entering TLSv1_2_client_method_ex
wolfSSL Entering wolfSSL_CTX_new_ex
wolfSSL Entering wolfSSL_Init
wolfSSL Entering wolfCrypt_Init
wolfSSL Entering wolfSSL_CertManagerNew
wolfSSL Leaving WOLFSSL_CTX_new, return 0
wolfSSL Entering wolfSSL_CTX_set_verify
wolfSSL Entering SSL_new
wolfSSL Leaving SSL_new, return 0
wolfSSL Entering SSL_connect()
wolfSSL Entering SendClientHello
Adding signature algorithms extension
growing output buffer
Signature Algorithms extension to write
Point Formats extension to write
Supported Groups extension to write
Encrypt-Then-Mac extension to write
EMS extension to write
Your IO Send callback is null, please set
wolfSSL Leaving SendClientHello, return -308
wolfSSL error occurred, error = -308
wolfSSL Entering SSL_get_error
wolfSSL Leaving SSL_get_error, return -308
SSL_connect failed
wolfSSL Entering SSL_write()
handshake not complete, trying to finish
wolfSSL Entering wolfSSL_negotiate
wolfSSL Entering SSL_connect()
Your IO Send callback is null, please set
wolfSSL error occurred, error = -308
wolfSSL Leaving wolfSSL_negotiate, return -1
wolfSSL Leaving SSL_write(), return -1
SSL_write failed
wolfSSL Entering wolfSSL_read()

What does that mean "Your IO Send callback is null, please set" i thought this was set up in "client-nb.c" with
"wolfSSL_SetIO_LwIP(ssl, sockfd, NULL, NULL, NULL);" api.
Although it is a little bit odd because the cb for recv and send are both NULL.
Do i have to place my own tcp recv and send function?

Thanks in advance