From: Patrick McHardy <kaber@trash.net>
To: "David S. Miller" <davem@davemloft.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [NETFILTER 03/05]: nf_conntrack: attach conntrack to TCP RST generated by ip6t_REJECT
Date: Thu, 16 Feb 2006 00:38:34 +0100 [thread overview]
Message-ID: <43F3BB7A.9060102@trash.net> (raw)
In-Reply-To: <20060215.152348.114993796.davem@davemloft.net>
David S. Miller wrote:
> From: Patrick McHardy <kaber@trash.net>
> 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.
>>
>
> Applied.
>
> Does the ipv4 REJECT target do this too?
>
Yes, IPv4 does the same for both TCP RSTs and ICMP errors.
next prev parent reply other threads:[~2006-02-15 23:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 23:00 [00/05]: Netfilter fixes for 2.6.16 Patrick McHardy
2006-02-15 23:00 ` [NETFILTER 01/05]: x_tables: fix dependencies of conntrack related modules Patrick McHardy
2006-02-15 23:21 ` David S. Miller
2006-02-15 23:00 ` [NETFILTER 02/05]: nf_conntrack: move registration of __nf_ct_attach Patrick McHardy
2006-02-15 23:22 ` David S. Miller
2006-02-15 23:00 ` [NETFILTER 03/05]: nf_conntrack: attach conntrack to TCP RST generated by ip6t_REJECT Patrick McHardy
2006-02-15 23:23 ` David S. Miller
2006-02-15 23:38 ` Patrick McHardy [this message]
2006-02-15 23:00 ` [NETFILTER 04/05]: nf_conntrack: attach conntrack to locally generated ICMPv6 error Patrick McHardy
2006-02-15 23:24 ` David S. Miller
2006-02-15 23:00 ` [NETFILTER 05/05]: nf_conntrack: Fix TCP/UDP HW checksum handling for IPv6 packet Patrick McHardy
2006-02-15 23:25 ` David S. Miller
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=43F3BB7A.9060102@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=netfilter-devel@lists.netfilter.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.