[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #34111] TCP_FIN_WAIT_TIMEOUT might be too small
From: |
Simon Goldschmidt |
Subject: |
[lwip-devel] [bug #34111] TCP_FIN_WAIT_TIMEOUT might be too small |
Date: |
Thu, 01 Sep 2011 08:11:04 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 5.1; rv:6.0.1) Gecko/20100101 Firefox/6.0.1 |
Update of bug #34111 (project lwip):
Status: None => Confirmed
Assigned to: None => goldsimon
_______________________________________________________
Follow-up Comment #6:
The fix proposed in comment #3 works for me (tested with Sysinternals TcpView,
the half open connections chance from close-wait to closed after receiving the
RST with correct seqno).
BTW, the code has been in there since the initial CVS revision...
Still, I'm curious about the FIN_WAIT2 timeout: where does it come from? Do
other stacks have such a timeout? Is the an additional RFC/spec (to the
original TCP RFC) which suggests such a timeout?
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?34111>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.nongnu.org/
- [lwip-devel] [bug #34111] TCP_FIN_WAIT_TIMEOUT might be too small,
Simon Goldschmidt <=