[lwip-devel] [patch #6865] SO_REUSEADDR for TCP

[Jeff Barber]

Follow-up Comment #5, patch #6865 (project lwip):

The only way I think that could happen (concurrent transfers with different
endpoints bound to the same local port) is when a listening endpoint accepts
two different connection requests.  In that case, both derive from the same
listening endpoint but the two are distinguishable because the *remote*
address/port is unique in each.

I don't think any platform allows multiple callers to bind different
endpoints to the same address/port combination.

The patch only allows the reuse of the port if the existing PCB using it is
already "dead".  (It's hanging around in TIME_WAIT only for the unusual cases
where the last ACK got lost or there is a duplicate stale packet wandering
around the net.)


    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/patch/?6865>

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