introduce new API for libnfnetlink
Pablo Neira Ayuso
maintainerRFC PATCH 1/1 introduce new API for libnfnetlink
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
Signature · 1 line
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
Quoted 18 lines · Pablo Neira Ayuso
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 netlinkADD_MEMBERSHIPsocket option to join multicast groups
- A new approach for challenge functions listen/talk, now they use the callbacks registered viaregister_callback()
- Single loop processing:nfnetlink_process()
- Iterators: more control for the programmer in the nfnetlink data processing
- addattr* simplification
- Documentation available
Quoted 3 lines
The patch is available at:
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