All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Jian <lark@linux.net.cn>
To: Amin Azez <azez@ufomechanic.net>
Cc: netfilter-devel@lists.netfilter.org,
	Pablo Neira <pablo@eurodev.net>,
	Patrick McHardy <kaber@trash.net>
Subject: Re: [PATCH] ct-event API port to 2.6.11
Date: Mon, 18 Apr 2005 19:13:43 +0800	[thread overview]
Message-ID: <20050418185959.037A.LARK@linux.net.cn> (raw)
In-Reply-To: <42639065.70809@ufomechanic.net>

Hi Amin Azez,

Pablo gave a patch the other day that patches pom-ng to get ctevent-api/.
I use this patch along with new nfnetlink/ and ctnetlink/, and it works
fine. Of course, you need to rename or symbol link ctevent-api/ to
conntrack-event-api/, because Harald Welte chooses it as name.

Execpt the ctevent-api, I think other parts have been put into new
nfnetlink/ and ctnetlink/.

Harald Welte also merged ctnetlink-conntrack_acct.patch, which seems to
do per stream packets/bytes counting stuff. (I just take a look at it,
so I may be wrong).


On Mon, 18 Apr 2005 11:48:05 +0100, Amin Azez <azez@ufomechanic.net> wrote:

> Pablo Neira wrote:
> > Pablo Neira wrote:
> > 
> >> Harald Welte wrote:
> >>
> >>> do you mind creating a patch against svn so we can put it into
> >>> nfnetlink-ctnetlink/linux-2.6.11 ?
> >>
> >>
> >>
> >> Attached two patches against pom-ng:
> >>
> >> o ctevent-api: conntrack event API
> >> o nfnetlink-ctnetlink: nfnetlink + conntrack netlink interface
> > 
> > oops, sorry, forgot the patches...
> 
> Can I just check that nfnetlink-ctnetlink-0.13 and 
> nfnetlink-ctnetlink-0.50 in pom-ng-20050404 have been replaced by
> pom-ng/nfnetlink and pom-ng/ctnetlink in pom-ng-20050417
> 
> Pablo, do they also fully supercede your patches 1-5 at 
> http://people.netfilter.org/~pablo/patches/nfnetlink-conntrack-0.50-2.6.11/ 
> and that there is nothing new in those?
> 
> If so, do you want me to create a pom-ng for the netlink packet counting 
> stuff I sent last week, our will you spit that out at an appropriate 
> point combined with your pattern defined dumping?
> 
> Sam



-- 
  lark

  reply	other threads:[~2005-04-18 11:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-27 23:55 [PATCH] ct-event API port to 2.6.11 Pablo Neira
2005-04-03 17:42 ` Patrick McHardy
2005-04-06 16:03   ` Amin Azez
2005-04-06 18:11     ` Pablo Neira
2005-04-07  4:17       ` Wang Jian
2005-04-07 12:34       ` Amin Azez
2005-04-07 14:21       ` Amin Azez
2005-04-07 16:28         ` Amin Azez
2005-04-08  9:15           ` Amin Azez
     [not found]             ` <42564FAA.2050302@eurodev.net>
     [not found]               ` <425658A8.6050200@ufomechanic.net>
2005-04-08 10:19                 ` Pablo Neira
2005-04-08 12:29                   ` Amin Azez
2005-04-08 12:46                     ` Pablo Neira
2005-04-08 13:50                       ` Amin Azez
2005-04-08 15:07                       ` Amin Azez
2005-04-08 15:13                         ` Amin Azez
2005-04-08 15:54                           ` Amin Azez
2005-04-10 20:45       ` Harald Welte
2005-04-12 14:50         ` Pablo Neira
2005-04-12 15:00           ` Pablo Neira
2005-04-18 10:48             ` Amin Azez
2005-04-18 11:13               ` Wang Jian [this message]
2005-04-18 11:06         ` 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=20050418185959.037A.LARK@linux.net.cn \
    --to=lark@linux.net.cn \
    --cc=azez@ufomechanic.net \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pablo@eurodev.net \
    /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.