[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #26062] FIN_WAIT_2 state following tcp_close should ti
[lwip-devel] [bug #26062] FIN_WAIT_2 state following tcp_close should timeout eventually
Fri, 03 Apr 2009 13:48:17 +0000
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:22.214.171.124) Gecko/2009032609 Firefox/3.0.8
Follow-up Comment #2, bug #26062 (project lwip):
True but there's only a single timer ("tmr") in the pcb and it gets updated
for each segment received. So if the remote end continues to send data after
we sent the FIN -- which is perfectly okay for it to do -- the session never
Since the intent of tcp_close is to permanently disconnect (as opposed to
"shutdown" semantics), then we should eventually force a connection close.
Otherwise, resources on both sides could remain allocated indefinitely.
Reply to this item at:
Message sent via/by Savannah