From: "David S. Miller" Subject: Re: [NETFILTER 03/05]: nf_conntrack: attach conntrack to TCP RST generated by ip6t_REJECT Date: Wed, 15 Feb 2006 15:23:48 -0800 (PST) Message-ID: <20060215.152348.114993796.davem@davemloft.net> References: <20060215230026.25078.33875.sendpatchset@localhost.localdomain> <20060215230031.25078.75252.sendpatchset@localhost.localdomain> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netfilter-devel@lists.netfilter.org Return-path: To: kaber@trash.net In-Reply-To: <20060215230031.25078.75252.sendpatchset@localhost.localdomain> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-devel-bounces@lists.netfilter.org Errors-To: netfilter-devel-bounces@lists.netfilter.org List-Id: netfilter-devel.vger.kernel.org From: Patrick McHardy Date: Thu, 16 Feb 2006 00:00:31 +0100 (MET) > [NETFILTER]: nf_conntrack: attach conntrack to TCP RST generated by ip6t_REJECT > > TCP RSTs generated by the REJECT target should be associated with the > conntrack of the original TCP packet. Since the conntrack entry is > usually not is the hash tables, it must be manually attached. > > Signed-off-by: Yasuyuki Kozakai > Signed-off-by: Patrick McHardy Applied. Does the ipv4 REJECT target do this too?