[lwip-devel] [bug #20640] Request getting lost/unanswered in lwip stack

[Kieran Mansley]

Follow-up Comment #6, bug #20640 (project lwip):

The PC reseting a connection after just 200ms is crazy, and totally breaks
TCP.  It basically means if there's any packet loss at all the connection will
get reset.  It prevents the TCP retransmission stuff ever getting a chance to
run and recover.  It also rides completely over the top of the TCP delayed ACK
mechanism, which could delay an ACK for 200ms.  This surely can't be standard
windows behaviour!

However, that doesn't explain why there's no response from the lwIP board in
that time.  I'm afraid that is going to be very hard to debug remotely in the
time available without knowledge of your hardware or port.  

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?20640>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/