[tproxy] EADDRNOTAVAIL from connect, but only sometimes

[Balazs Scheidler]

On Thu, 2010-04-15 at 08:58 -0400, Ron Parker wrote:
> Yes, the exact port numbers are used in an attempt to maximize transparency.   The SO_REUSEADDR only allows the bind to proceed, but the connect still fails due to the socket with the matching 4-tuple being in the time_wait state.   Would tcp_tw_recycle/tcp_tw_reuse help in this case?
> 

TIME_WAIT shouldn't be an issue. It is ignored if SO_REUSEADDR is
specified.

But REUSEADDR must be specified for both sockets, but I guess that's the
case.

-- 
Bazsi