From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Cc: lwn@lwn.net
Subject: [ANNOUNCE] libmnl 1.0.4 release
Date: Sat, 2 Jul 2016 11:11:42 +0200 [thread overview]
Message-ID: <20160702091142.GA2457@salvia> (raw)
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
Hi!
The Netfilter project presents:
libmnl 1.0.4
libmnl is a minimalistic user-space library oriented to Netlink
developers. There are a lot of common tasks in parsing, validating,
constructing of both the Netlink header and TLVs that are repetitive
and easy to get wrong. This library aims to provide simple helpers
that allows you to re-use code and to avoid re-inventing the wheel.
This release comes with improvements in the netlink message printing
function, attribute validation for MNL_TYPE_MSEC and MNL_TYPE_U64,
clang compilation fixes, the new mnl_socket_open2() and
mnl_socket_fdopen() functions, missing handling for NLM_F_DUMP_INTR
and documentation updates.
See ChangeLog that comes attached to this email for more details.
You can download it from:
http://www.netfilter.org/projects/libmnl/downloads.html
ftp://ftp.netfilter.org/pub/libmnl/
Have fun!
[-- Attachment #2: changes-libmnl-1.0.4.txt --]
[-- Type: text/plain, Size: 2179 bytes --]
Carlos Falgueras García (1):
nlmsg: Improve payload printing
Eric Leblond (1):
doxygen: fix a variable name.
Felix Janda (1):
examples/netfilter: Include <endian.h> for be64toh
Guillaume Nault (1):
socket: introduce mnl_socket_open2()
Gustavo Zacarias (1):
configure: uclinux is also linux
Hisao Tanabe (1):
attr: minor doc fix in mnl_attr_next()
Ken-ichirou MATSUZAWA (9):
examples: set attr table
examples: fix trivial error message
examples: use mnl_nlmsg_get_payload()
attr: validate MNL_TYPE_MSEC same as MNL_TYPE_U64
examples: made sub functions the same
examples: fix display condition
examples: use mnl_socket_setsockopt
socket: creating a struct mnl_socket from a pre-existing socket
doc: minor fix
Markus Teich (1):
header: use sysconf() instead of getpagesize()
Pablo Neira Ayuso (18):
examples: add genl-group-events
examples: add kobject-event
examples: rtnl-route-add improvements (including IPv6 support)
examples: rtnl-route-event: add example to listen to IPv4/IPv6 routes
examples: rtnl-route-event: update Makefile.am
examples: rtnl-route-add: fix typo in IPv6 support
examples: rtnl-route-dump: display also metric/priority
examples: rtnl-link-dump: display HW address
examples: add rtnl-addr-dump
examples: netfilter: add nfct-dump
include: cache copy of nfnetlink_conntrack.h
examples: netfilter: add nfct daemon skeleton code
include: don't force compiler to enter C++11 mode
include: cache copy of include/linux/socket.h
socket: calloc expects struct size as second parameter
example: netfilter: get rid of aligned_be64 definitions
src: cleanup function definitions
build: libmnl 1.0.4 release
Peter Foley (1):
Move declaration of visibility attributes before definition.
Philip Prindeville (1):
examples: rtnl-route-dump: add IPv6 support
Shawn Landden (1):
doc: mnl_socket_open returns NULL on error
Stephen Hemminger (2):
headers: update netlink.h to 3.9
callback: fix missing handling of NLM_F_DUMP_INTR
reply other threads:[~2016-07-02 9:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160702091142.GA2457@salvia \
--to=pablo@netfilter.org \
--cc=lwn@lwn.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).