Kev-Jiang

Another question: Why use LwIP Raw API instead of Socket API? Using Socket API might improve compatibility and portability.

I feel that libcoap has many issues when running on lwIP, especially with TCP. Although I am working with common usage scenarios, it seems quite challenging to use it directly....

Issue Summary: I discovered a new lwip issue where CoAP experiences probabilistic crashes during TCP connection establishment. Log Fragment: ``` tcp_bind: bind to port 49916\n tcp_connect to port 5683\n tcp_enqueue_flags:...

For new issue, I need to first emphasize and add a detail: this issue is probabilistic in nature. I later conducted a 4-hour stress test and successfully reproduced the problem....

Regarding your modification in https://github.com/obgm/libcoap/pull/1827, there's one part I don't quite understand: why do you need to increment the window by 1 (tcp_recved(sock->tcp_pcb, 1);) when p==NULL in coap_tcp_recv? I haven't...

I discovered another probabilistic issue: Although `coap_lwip_tcp_close` already contains `tcp_err(tcp_pcb, NULL); tcp_arg(tcp_pcb, NULL);` But when the server is in call-home mode, if it fails to connect from the beginning, 6...

> If you make something similar to the following change to the LwIP code, then the logging will report the thread id so we can see if there is a...

> Re [#1826 (comment)](https://github.com/obgm/libcoap/issues/1826#issuecomment-3631578485), I think that this is missing > > ``` > diff --git a/src/coap_strm_lwip.c b/src/coap_strm_lwip.c > index 7b9879be..d6b50203 100644 > --- a/src/coap_strm_lwip.c > +++ b/src/coap_strm_lwip.c > @@...

@mrdeep1 # Regarding the interruption of tcp_output in tcp_connect by tcp_slowtmr, I have some thoughts: ## Issue: Race Conditions in TCP Operations and Missing LOCK_TCPIP_CORE() Protection in lwIP Integration ###...

> 3 new events are in the latest code > > ``` > /* > * Reconnect events > */ > /** Triggered when a session failed, and a reconnect...