[lwip-devel] [bug #26062] FIN_WAIT_2 state following tcp_close should timeout eventually

[Jeff Barber]

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
times out.

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:

  <http://savannah.nongnu.org/bugs/?26062>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/