Re: [lwip-users] serious lwIP 1.4.0 error

[Valery Ushakov]

Peter Sprenger <address@hidden> wrote:

> The lwIP 1.4.0 problem is (I am using raw API), that lwIP gets a
> [FIN,ACK] from the other side (Firefox), but instead of doing a
> tcp_sent callback, it resubmits 3 times the packet that was already
> acked in the [FIN,ACK]. This leads to a hanging half-closed situation.
> Only after some minutes the Firefox on the PC will close the
> connection. Do you know if this has been fixed?

Stupid question, but are you sure the FIN|ACK datagram actually
reaches lwIP tcpip thread?  You may be out of MEMP_NUM_TCPIP_MSG_INPKT.
I ran into this a few times with similar symptoms - lwIP would
retransmit data that looks ACKed if you only check the tcpdump trace.

-uwe