[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [bug #50837] LWIP TCP/IP race condition

From: Simon Goldschmidt
Subject: [lwip-devel] [bug #50837] LWIP TCP/IP race condition
Date: Fri, 21 Apr 2017 15:38:50 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Follow-up Comment #10, bug #50837 (project lwip):

Joel, thanks for that excellent analysis. I wonder why the Win/Python client
doesn't re-send that ACK. Is there something wrong with our implementation of
RFC 5961 section 3.2?

Preet, the mbox holds pbufs pointers. Increasing the mbox size indeed does not
help much as you can get into this situation at any time. You would have to
set mbox size to your window's size as any byte could come in in one

In fact, the segments dropped by lwIP could in fact have been dropped by the
network. In that case, we would have a zombie pcb without doing anything wrong
other than protecting against the RST spoofing attack!


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]