From: Patrick McHardy <kaber@trash.net>
To: KOVACS Krisztian <hidden@balabit.hu>
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH 1/3] tproxy: kick out TIME_WAIT sockets in case a new connection comes in with the same tuple
Date: Thu, 21 Oct 2010 12:45:58 +0200 [thread overview]
Message-ID: <4CC019E6.10202@trash.net> (raw)
In-Reply-To: <20101020112142.6538.90622.stgit@este.odu>
Am 20.10.2010 13:21, schrieb KOVACS Krisztian:
> 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.
Applied, thanks.
prev parent reply other threads:[~2010-10-21 10:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 11:21 [PATCH 0/3] tproxy fixes for current upstream code KOVACS Krisztian
2010-10-20 11:21 ` [PATCH 2/3] tproxy: add lookup type checks for UDP in nf_tproxy_get_sock_v4() KOVACS Krisztian
2010-10-21 10:48 ` Patrick McHardy
2010-10-20 11:21 ` [PATCH 3/3] tproxy: fix hash locking issue when using port redirection in __inet_inherit_port() KOVACS Krisztian
2010-10-21 11:08 ` Patrick McHardy
2010-10-20 11:21 ` [PATCH 1/3] tproxy: kick out TIME_WAIT sockets in case a new connection comes in with the same tuple KOVACS Krisztian
2010-10-21 10:45 ` Patrick McHardy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CC019E6.10202@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=hidden@balabit.hu \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.