From: Patrick McHardy <kaber@trash.net>
To: Yasuyuki KOZAKAI <yasuyuki.kozakai@toshiba.co.jp>
Cc: netfilter-devel@lists.netfilter.org, usagi-core@linux-ipv6.org,
laforge@gnumonks.org
Subject: Re: [PATCH 0/3] nf_conntrack: fixes for nf_ct_attach in IPv6 stack
Date: Tue, 14 Feb 2006 17:26:32 +0100 [thread overview]
Message-ID: <43F204B8.5060700@trash.net> (raw)
In-Reply-To: <200602140348.k1E3msEc020481@toshiba.co.jp>
Yasuyuki KOZAKAI wrote:
> From: Patrick McHardy <kaber@trash.net>
> Date: Mon, 13 Feb 2006 17:44:30 +0100
>
>>
>>The reason why we manually attach these references (at least for ICMP)
>>is because the packet might be in the middle of two NAT manips and
>>unrecognizable for conntrack. For IPv6 this should be irrelevant. I'm
>>not sure why it is done for TCP RSTs, they should always be properly
>>tracked anyway.
>
>
> It's common case for me that the conntrack of original TCP packet is
> unconfirmed at processing in REJECT target. In this case, TCP RST
> generated by REJECT causes to create new conntrack. I don't think
> that is good behavior. That can be said about sending ICMPv6 error.
Unless I'm missing something, that shouldn't happen.
__{ip,nf}_conntrack_confirm check that the packet is in direction
IP_CT_DIR_ORIGINAL before confirming the conntrack.
next prev parent reply other threads:[~2006-02-14 16:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200602131628.k1DGSpc3019846@toshiba.co.jp>
2006-02-13 16:44 ` [PATCH 0/3] nf_conntrack: fixes for nf_ct_attach in IPv6 stack Patrick McHardy
2006-02-14 3:48 ` Yasuyuki KOZAKAI
[not found] ` <200602140348.k1E3msEc020481@toshiba.co.jp>
2006-02-14 16:26 ` Patrick McHardy [this message]
2006-02-14 17:59 ` Yasuyuki KOZAKAI
[not found] ` <200602141759.k1EHxfk0009760@toshiba.co.jp>
2006-02-14 18:13 ` Patrick McHardy
2006-02-14 18:35 ` Yasuyuki KOZAKAI
2006-02-14 20:41 ` Jozsef Kadlecsik
2006-02-15 7:47 ` Harald Welte
2006-02-15 9:01 ` Patrick McHardy
2006-02-15 10:10 ` Patrick McHardy
2006-02-13 16:28 Yasuyuki KOZAKAI
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=43F204B8.5060700@trash.net \
--to=kaber@trash.net \
--cc=laforge@gnumonks.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=usagi-core@linux-ipv6.org \
--cc=yasuyuki.kozakai@toshiba.co.jp \
/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.