From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Cc: Harald Welte <laforge@netfilter.org>, Patrick McHardy <kaber@trash.net>
Subject: [RFC,PATCH] introduce new API for libnfnetlink
Date: Mon, 19 Jun 2006 01:26:58 +0200 [thread overview]
Message-ID: <4495E142.5000209@netfilter.org> (raw)
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
This is still a work in progress, it needs more testing. I have plans to
do something similar for libnetfilter_conntrack in order to solve the
existing limitations.
Comments welcome.
[1] http://patchwork.netfilter.org/netfilter-devel/patch.pl?id=3315
--
The dawn of the fourth age of Linux firewalling is coming; a time of
great struggle and heroic deeds -- J.Kadlecsik got inspired by J.Morris
next reply other threads:[~2006-06-18 23:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 23:26 Pablo Neira Ayuso [this message]
2006-06-21 16:24 ` [RFC,PATCH] introduce new API for libnfnetlink 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=4495E142.5000209@netfilter.org \
--to=pablo@netfilter.org \
--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.