From: Amin Azez <azez@ufomechanic.net>
To: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH 1/2] flow match for 2.6.11
Date: Tue, 12 Jul 2005 17:36:47 +0100 [thread overview]
Message-ID: <db0rj4$q4h$1@sea.gmane.org> (raw)
In-Reply-To: <42D3B9C7.1070507@ufomechanic.net>
I'm backporting this to 2.6.11 as I see the conntrack-event-api in
pom-ng SVN for 2.6.11 is the same as for 2.6.12 apart from ftp sequence
number adjusting takes a 32bit parameter in 2.6.12, and your patches
apply cleanly.
I'm just tracking down why function ipct_flow_inc gets called with quite
different events parameter under 2.6.11 for a connection than under 2.6.12
It gets called 4 times for a new connection, 2.6.11
(EVENTS is hex)
FLOW INC ipct_flow_inc 341 EVENTS=471[ new=1, related=2]
FLOW INC ipct_flow_inc 341 EVENTS=78[ new=1, related=2]
FLOW INC ipct_flow_inc 341 EVENTS=401[ new=1, related=2]
FLOW INC ipct_flow_inc 341 EVENTS=18[ new=1, related=2]
compared with 2.6.12
FLOW INC ipct_flow_inc 341 EVENTS=471[ new=1, related=2]
FLOW INC ipct_flow_inc 341 EVENTS=411[ new=1, related=2]
Anyway, I mention it in case you have any hints.
Amin
next prev parent reply other threads:[~2005-07-12 16:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 23:49 [PATCH 1/2] flow match Josh Samuelson
2005-06-29 19:18 ` Pablo Neira
2005-06-30 1:04 ` Patrick McHardy
2005-06-30 2:53 ` Josh Samuelson
2005-07-11 15:08 ` Amin Azez
2005-07-11 16:10 ` Amin Azez
2005-07-12 12:38 ` [PATCH 1/2] flow match feedback Amin Azez
2005-07-12 16:36 ` Amin Azez [this message]
[not found] ` <20050712221137.GB8298@wsc.edu>
2005-07-13 9:23 ` Amin Azez
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='db0rj4$q4h$1@sea.gmane.org' \
--to=azez@ufomechanic.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.