ESP32/ENC28J60/EthernetENC: BearSSL "incoming record is too large to be processed, or buffer is too small" #22
-
In my setup ESP32/ENC28J60/EthernetENC I am seeing the following when communicating with some servers.
Socket connection succeeds (i.e. It seems to come from here: https://github.com/khoih-prog/EthernetWebServer_SSL/blob/main/src/SSLClient/bearssl/src/ssl/ssl_engine.c#L688 I added a
Which of the buffers do I need to increase in this case? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
It's possible the ENC28J60 has to do many (uIP) jobs by software and slow down the TLS/SSL encryption/decryption process => overflowing the buffer. It's very deep inside the I suggest that you use the better W5500, or even the best LAN8720 in WT32_ETH01, to see if OK then. You also can post question and ask for help at EthernetENC and/or OPEnSLab-OSU SSLClient |
Beta Was this translation helpful? Give feedback.
It's possible the ENC28J60 has to do many (uIP) jobs by software and slow down the TLS/SSL encryption/decryption process => overflowing the buffer.
It's very deep inside the
BEARSSL
code and also (server) use-case-dependent, and will take some time to debug to know where and when it happens and fix.I suggest that you use the better W5500, or even the best LAN8720 in WT32_ETH01, to see if OK then.
Using
WT32_ETH01 (ESP22 + LAN8720)
you can use better and faster native SSL of ESP32.You also can post question and ask for help at EthernetENC and/or OPEnSLab-OSU SSLClient