netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 2/2] netfilter: ctnetlink: fix wrong message type in user updates
Date: Tue, 05 May 2009 17:49:06 +0200	[thread overview]
Message-ID: <4A005FF2.7010502@trash.net> (raw)
In-Reply-To: <20090505131429.7241.88268.stgit@Decadence>

Pablo Neira Ayuso wrote:
> This patch fixes the wrong message type that are triggered by
> user updates, the following commands:
> 
> (term1)# conntrack -I -p tcp -s 1.1.1.1 -d 2.2.2.2 -t 10 --sport 10 --dport 20 --state LISTEN
> (term1)# conntrack -U -p tcp -s 1.1.1.1 -d 2.2.2.2 -t 10 --sport 10 --dport 20 --state SYN_SENT
> (term1)# conntrack -U -p tcp -s 1.1.1.1 -d 2.2.2.2 -t 10 --sport 10 --dport 20 --state SYN_RECV
> 
> only trigger event message of type NEW, when only the first is NEW
> while others should be UPDATE.
> 
> (term2)# conntrack -E
>     [NEW] tcp      6 10 LISTEN src=1.1.1.1 dst=2.2.2.2 sport=10 dport=20 [UNREPLIED] src=2.2.2.2 dst=1.1.1.1 sport=20 dport=10 mark=0
>     [NEW] tcp      6 10 SYN_SENT src=1.1.1.1 dst=2.2.2.2 sport=10 dport=20 [UNREPLIED] src=2.2.2.2 dst=1.1.1.1 sport=20 dport=10 mark=0
>     [NEW] tcp      6 10 SYN_RECV src=1.1.1.1 dst=2.2.2.2 sport=10 dport=20 [UNREPLIED] src=2.2.2.2 dst=1.1.1.1 sport=20 dport=10 mark=0
> 
> This patch also removes IPCT_REFRESH from the bitmask since it is
> not of any use.

Also applied, thanks.

      reply	other threads:[~2009-05-05 15:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-05 13:13 [PATCH 0/2] netfilter fixes for 2.6.30-rc Pablo Neira Ayuso
2009-05-05 13:14 ` [PATCH 1/2] netfilter: iptables: fix use of cluster match with 32 nodes Pablo Neira Ayuso
2009-05-05 15:47   ` Patrick McHardy
2009-05-05 13:14 ` [PATCH 2/2] netfilter: ctnetlink: fix wrong message type in user updates Pablo Neira Ayuso
2009-05-05 15:49   ` 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=4A005FF2.7010502@trash.net \
    --to=kaber@trash.net \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).