From: Michael Bellion and Thomas Heinz <nf@hipac.org>
To: netfilter@lists.netfilter.org, netfilter-devel@lists.netfilter.org
Subject: [ANNOUNCE] nf-hipac v0.8 released
Date: Wed, 25 Jun 2003 22:12:49 +0200 [thread overview]
Message-ID: <200306252212.49588.nf@hipac.org> (raw)
Hi
We have just released a new version of nf-hipac. You might wonder why
this lasted so long. Well, we did a major rewrite of most of the code,
added a bunch of new features and did heavy userspace testing of the
algorithmic core.
For all of you who don't know nf-hipac yet, here is a short overview:
nf-hipac is a drop-in replacement for the iptables packet filtering module.
It implements a novel framework for packet classification which uses an
advanced algorithm to reduce the number of memory lookups per packet.
The module is ideal for environments where large rulesets and/or high
bandwidth networks are involved. Its userspace tool, which is also called
'nf-hipac', is designed to be as compatible as possible to 'iptables -t
filter'.
The official project web page is: http://www.hipac.org
The releases can be downloaded from: http://sourceforge.net/projects/nf-hipac
Here is a short overview of the new features:
- generic support for iptables targets and matches:
nf-hipac is now binary compatible to iptables targets and
matches.
- support for user defined chains:
This was a real challenge.
- 64 bit atomic counters:
We avoided cache ping-pong on SMP machines.
- nf-hipac connection tracking helper:
This is basically a dummy module which avoids that you
manually load ip_conntrack.
- extended proc statistics
- libnfhipac:
We've implemented a very lightweight userspace library which
does the netlink communication for you, so writing an alternative
userspace tool for nf-hipac is simplified. [you still have to
construct the rule which is sent to the kernel]
- new netlink based protocol:
Apart from that it was necessary to redesign the protocol
to support the new features we have improved the listing speed
by putting as many rules/chains in a packet as possible.
- non-terminal rule support:
The nf-hipac rule target is optional.
Basically, nf-hipac now offers the same functionality as iptables -t filter
apart from the RETURN target which is missing and some minor
user-defined chain related issues.
Unfortunately we discovered an alignment bug in the btree layer
(the only part we haven't rewritten) which breaks architectures
requiring strict alignment for pointers (like alpha).
Sparc64 again seems to work fine.
Enjoy,
+-----------------------+----------------------+
| Michael Bellion | Thomas Heinz |
| <mbellion@hipac.org> | <creatix@hipac.org> |
+-----------------------+----------------------+
next reply other threads:[~2003-06-25 20:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 20:12 Michael Bellion and Thomas Heinz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-25 20:48 [ANNOUNCE] nf-hipac v0.8 released Michael Bellion and Thomas Heinz
2003-06-25 21:03 ` Folkert van Heusden
2003-06-25 23:52 ` Thomas Heinz
2003-06-26 13:38 ` Daniel Egger
2003-06-26 14:20 ` Michael Bellion and Thomas Heinz
2003-06-26 14:45 ` Daniel Egger
2003-06-27 6:06 ` Pekka Savola
2003-06-28 20:04 ` Michael Bellion and Thomas Heinz
2003-06-29 6:26 ` Pekka Savola
2003-06-29 7:45 ` Roberto Nibali
2003-06-29 16:26 ` Michael Bellion and Thomas Heinz
2003-07-02 5:30 ` Pekka Savola
2003-07-02 12:26 ` Michael Bellion and Thomas Heinz
2003-07-02 13:08 ` P
2003-07-02 13:48 ` Michael Bellion and Thomas Heinz
2003-07-02 14:23 ` P
2003-07-02 16:57 ` Michael Bellion and Thomas Heinz
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=200306252212.49588.nf@hipac.org \
--to=nf@hipac.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=netfilter@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.