On Fri, 2009-01-23 at 17:45 +0100, Simon Goldschmidt wrote: > You should check your port and driver for correctness first. Of course > it could also be a bug in lwIP, but things like "I cannot turn on all > TCP debug as this will cause the stack not to work at all" are highly > suspicious of threading problems!
Although there are some parts of the TCP protocol that rely on timing, and if you're spending a lot of time printing out debug statements your could fail to meet these constraints and the other end could quite rightly give up. It would be interesting to see a packet capture around the point that the connection is prematurely closed. The move directly to CLOSED from ESTABLISHED makes me think that there might be a TCP RST segment involved. Kieran _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
