tproxy: kick out TIME_WAIT sockets in case a new connection comes in with the same...
authorBalazs Scheidler <bazsi@balabit.hu>
Thu, 21 Oct 2010 10:45:14 +0000 (12:45 +0200)
committerPatrick McHardy <kaber@trash.net>
Thu, 21 Oct 2010 10:45:14 +0000 (12:45 +0200)
commit106e4c26b1529e559d1aae777f11b4f8f7bafc26
treee784c61379e767255bf941f9d78d9ef6e7c58640
parentd86bef73b4a24e59e7c1f896a72bbf38430ac2c6
tproxy: kick out TIME_WAIT sockets in case a new connection comes in with the same tuple

Without tproxy redirections an incoming SYN kicks out conflicting
TIME_WAIT sockets, in order to handle clients that reuse ports
within the TIME_WAIT period.

The same mechanism didn't work in case TProxy is involved in finding
the proper socket, as the time_wait processing code looked up the
listening socket assuming that the listener addr/port matches those
of the established connection.

This is not the case with TProxy as the listener addr/port is possibly
changed with the tproxy rule.

Signed-off-by: Balazs Scheidler <bazsi@balabit.hu>
Signed-off-by: KOVACS Krisztian <hidden@balabit.hu>
Signed-off-by: Patrick McHardy <kaber@trash.net>
include/net/netfilter/nf_tproxy_core.h
net/netfilter/nf_tproxy_core.c
net/netfilter/xt_TPROXY.c
net/netfilter/xt_socket.c