-
Notifications
You must be signed in to change notification settings - Fork 5
Description
Hi, again
based on wolfssl-sever , everything works flawlessly on single instance . I have a challenge while implementing a multi-client https server using wolfSSL on an Ethernet-based platform.
the https server needs to support multiple simultaneous client connections over Ethernet using TLS. The server utilizes:
- A single
WOLFSSL_CTX
instance. - Multiple
WOLFSSL
objects (one per client). - Custom I/O callbacks (
EthernetSend
andEthernetReceive
) for communication.
Observed Issues:
-
during data transmission or reception, the callbacks sometimes fail to correctly associate the incoming
WOLFSSL
object with the intended client connection. -
With multiple clients, I frequently observe the debug log
wolfSSL Entering RetrySendAlert
, which seems to indicate issues with retrying alerts during communication.
Suggested fixes
- Use specific Ethernet callbacks (
EthernetSend
andEthernetReceive
) to handle multi_client communication. - Observe incorrect callback behavior, overwritten connections, or handshake
Thank you for providing such a robust and lightweight SSL/TLS library. I appreciate your time and support . Please let me know if you need additional details or a code example to replicate the behavior.
Best regards,