All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Leblond <eric@inl.fr>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: laforge@netfilter.org, netfilter-devel@lists.netfilter.org,
	haypo@inl.fr, Patrick McHardy <kaber@trash.net>,
	vincent@inl.fr
Subject: Re: [PATCH] Set mark to 0 from libnetfilter_conntrack
Date: Fri, 27 Oct 2006 23:17:13 +0200	[thread overview]
Message-ID: <1161983833.16181.6.camel@localhost> (raw)
In-Reply-To: <45420F5B.8090504@netfilter.org>

[-- Attachment #1: Type: text/plain, Size: 1617 bytes --]

Hi,

Le vendredi 27 octobre 2006 à 15:53 +0200, Pablo Neira Ayuso a écrit :
> Eric Leblond wrote:
> > What's the status of this new API ? Current status of
> > libnetfilter_conntrack code is really disappointing.
> 
> Indeed, you can blame me for that. I'm working on the new API that I'll 
> try to release asap. I'm going to put this in my high priority queue.

That's good news !

> 
> > We at INL are currently working on using libnetfilter_conntrack to
> > provide tools for firewall administrators. The first one
> > pynetfilter_conntrack is already available and a web management
> > interface will soon be released. By doing this we are trying to improve
> > the usability of this new system.
> 
> I'd like to see your python binding in the libnetfilter_conntrack tree 
> but I have to fix some stuff before, please consider that this would 
> require some extra work from your part.

No problem. We really think it's the correct place for this code and it
will worth the work to put it there.

> 
> > We are doing this because we think the new features provided by
> > libnetfilter_conntrack really improve a lot the way we use and "live"
> > with a Netfilter firewall.
>
> I already commented what my intentions are: add more new API, do not 
> remove the old one but mark it as deprecated, strongly recommend people 
> to move to the new API. The deprecated API will be removed after quite 
> some time.

Is it possible to introduce a version number of the API in a #define to
be able to do some conditional compilations ?

BR,
-- 
Eric Leblond <eric@inl.fr>
INL

[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

      reply	other threads:[~2006-10-27 21:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-25 18:38 [PATCH] Set mark to 0 from libnetfilter_conntrack Eric Leblond
2006-10-25 23:37 ` Patrick McHardy
2006-10-26 21:37   ` Eric Leblond
2006-10-27 13:53     ` Pablo Neira Ayuso
2006-10-27 21:17       ` Eric Leblond [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=1161983833.16181.6.camel@localhost \
    --to=eric@inl.fr \
    --cc=haypo@inl.fr \
    --cc=kaber@trash.net \
    --cc=laforge@netfilter.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pablo@netfilter.org \
    --cc=vincent@inl.fr \
    /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.