|
From: | Joel Cunningham |
Subject: | [lwip-devel] [bug #49533] TCP connection deadlocks upon dropped window update due to not filling window |
Date: | Mon, 14 Nov 2016 15:27:56 +0000 (UTC) |
User-agent: | Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0 |
Follow-up Comment #3, bug #49533 (project lwip): Simon, I'm fine with starting the persistent timer in the specific case I've identified. I'm a little surprised at the suggestion because this was LwIP's legacy behavior which was removed in bug #34517 (commit d8f090a7595a79050c435545d00efc1261b9691c). Are you more comfortable with using the persistent timer with the extra conditions I've identified (making sure wnd is snd.wnd and pcb->unacked == NULL)? The old behavior would start the timer at the end of sending a window's worth of data if there was still a segment that didn't fit I can do some testing with this solution in my test environment. _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/bugs/?49533> _______________________________________________ Message sent via/by Savannah http://savannah.nongnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |