We've been studying the debug info the lwipstack provides and noticed that this happens with multiple threads to the stack.
Sometimes a "tcp_receive: received FIN" isn't followed by TCP connection closed 3613 -> 80. tcp_pcb_purge This would mean the buffers aren't purged and wouldn't this end up in a loop in netconn_write() because len = 0 due to unpurged data in the send buffer? Grtz Edwin _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
