All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amin Azez <azez@ufomechanic.net>
To: netfilter-devel@lists.netfilter.org
Cc: Harald Welte <laforge@netfilter.org>, Patrick McHardy <kaber@trash.net>
Subject: Re: [RFC,PATCH] introduce new API for libnfnetlink
Date: Wed, 21 Jun 2006 17:24:47 +0100	[thread overview]
Message-ID: <449972CF.6060402@ufomechanic.net> (raw)
In-Reply-To: <4495E142.5000209@netfilter.org>

Pablo Neira Ayuso wrote:
> Hi!
> 
> I have been spending some time on libnfnetlink these days based on a
> previous patch that I sent some time ago [1]. Since the amount of
> changes would result in API breakages, that is something that I consider
> that we don't want, I decided to start some kind of version 2 of
> libnfnetlink, the major changes from the current version is:
> 
> - Uniform error handling via errno
> - Use of new netlink ADD_MEMBERSHIP socket option to join multicast groups
> - A new approach for challenge functions listen/talk, now they use the
> callbacks registered via register_callback()
> - Single loop processing: nfnetlink_process()
> - Iterators: more control for the programmer in the nfnetlink data
> processing
> - addattr* simplification
> - Documentation available
> 
> The patch is available at:
> 
> http://people.netfilter.org/pablo/libnfnetlink-newapi.patch

Thanks for this Pablo.

As long as there is still a way to exit the message reading loop at the
end of the current packet (without discarding any messages), then it
will suit me.

I'm using the old conntrack API by receiving events and periodic dumps
of all conntracks over the same netlink. At certain times a signal goes
off which sets a flag to exit the read loop after the current netlink
packet, then a conntrack dump is requested and the readloop is re-entered.

I suppose this will still be possible?

Sam

      reply	other threads:[~2006-06-21 16:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-18 23:26 [RFC,PATCH] introduce new API for libnfnetlink Pablo Neira Ayuso
2006-06-21 16:24 ` Amin Azez [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=449972CF.6060402@ufomechanic.net \
    --to=azez@ufomechanic.net \
    --cc=kaber@trash.net \
    --cc=laforge@netfilter.org \
    --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.