Hi Simon,
I am using LWIP-2.1.2
TCP_Dup_Ack_FIN_ACK_RST.pcapng
<http://lwip.100.n7.nabble.com/file/t1901/TCP_Dup_Ack_FIN_ACK_RST.pcapng>  I
read through this thread, and I am having a problem similar to the one
described here..

Description: 
"LWIP stack at client at some point skips an expected segment (tcp pkt of
1460 bytes length) and server sends a dup ack requesting for the missing
segment. However, LWIP stack still does not send it and remained silent for
over 500msec. At this point, server triggers a connection close. More than a
second after the connection close handshake, client sends the missing
segment which triggers the server to reset the connection. LWIP stack
invokes callbacks into the iperf_client which is what is seen in the console
logs".



--
Sent from: http://lwip.100.n7.nabble.com/lwip-users-f3.html

_______________________________________________
lwip-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lwip-users

Reply via email to