yeah, 1.web server is RAW API, and we do call the API in the same thread ,say tcpip_thread; we use socket APIs in other threads. we can ensure that all the APIs is called properly in our multithreaded system.
2.we did post the capture files “wireshark.pcapng” ,which is just above the snapshots. 3.right, NO_SYS = 0; we have tested all of our lwip related applications, like tcp client, tcp server, udp, sntp, which are running in our system at the same time, for several weeks , all ok, except for web server. 4.The problem I described happens not all the time, but occasionally. Thus the original simple example may work all the time. Our web server is based on that example just with much more communication throughput. thanks. -- View this message in context: http://lwip.100.n7.nabble.com/http-server-problems-bug-tp26999p27006.html Sent from the lwip-users mailing list archive at Nabble.com. _______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users