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

[Simon Goldschmidt]

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

Agree about TIME_WAIT, especially as it doesn't hurt: when allocating a new
pcb and running out of resources, TIME_WAIT pcbs are killed anyway.

Reading about SO_REUSERADDR vs. SO_REUSEPORT, am I correct that SO_REUSEPORT
is not necessary since it's not standardised and mostly does the same?

And it seems that our SO_REUSEADDR for TCP is still missing the 2 points you
wrote (binding to different local IPs, binding listen pcbs to ports used by
non-listen pcbs)?

About the latter case: how can bind() detect that, it would allow 2
connection pcb (i.e. non-listen) to bind to the same local address, wouldn't
it? If the 5-tuple must be unique, then connect() (and maybe accept(), too?)
would have to check the remote address (only if SO_REUSEADDR is set) to
prevent a non-unique 5-tuple!

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.nongnu.org/