All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Jian <lark@linux.net.cn>
To: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH 2/2] Port nfnetlink and nfnetlink_conntrack to 2.6
Date: Wed, 30 Mar 2005 23:57:29 +0800	[thread overview]
Message-ID: <20050330235438.01A4.LARK@linux.net.cn> (raw)
In-Reply-To: <4247481F.9090702@eurodev.net>

Hi Pablo Neira,

I want to use nfnetlink-ctnetlink to keep track of successful session in
a project. Can you make it avaible in pom-ng?

Thanks.

On Mon, 28 Mar 2005 01:56:15 +0200, Pablo Neira <pablo@eurodev.net> wrote:

> Comments about changes:
> 
> o Minor change: my compiler (gcc-2.95) complained about ct_debug so I 
> inserted the classical DEBUGP macro.
> 
> o No important modifications in nfnetlink.c
> 
> o Added support to identify conntracks by id.
> 
> o Removed ordered list, now we just insert a unsigned int in struct 
> ip_conntrack to hold the id. Now the table dumping is done iterating the 
> hash table.
> 
> o Adaptation to ct-event API
> 
> o improved way to delete a conntrack (marcus sundberg)
> 
> o kill [dump|change]_natinfo, now that must be handle in 
> [dump|change]_status.
> 
> o IMPORTANT: I haven't tested expectation handling.
> 
> Things I consider to do:
> 
> o split CTNL_MSG_GETCONNTRACK to two messages types: 
> CTNL_MSG_GETCONNTRACK and CTNL_MSG_DMPCONNTRACK (dump)
> 
> o split CTNL_MSG_NEWCONNTRACK to two messages types: 
> CTNL_MSG_NEWCONNTRACK and CTNL_MSG_UPDCONNTRACK (update)
> 
> o Move nfnetlink.h and nfnetlink_conntrack.h to netfilter/ directory.



-- 
  lark

      reply	other threads:[~2005-03-30 15:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-27 23:56 [PATCH 2/2] Port nfnetlink and nfnetlink_conntrack to 2.6 Pablo Neira
2005-03-30 15:57 ` Wang Jian [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=20050330235438.01A4.LARK@linux.net.cn \
    --to=lark@linux.net.cn \
    --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.