From: Eric Leblond <eric@regit.org>
To: netfilter-devel@vger.kernel.org, pablo@netfilter.org
Cc: eric@regit.org
Subject: [nftables PATCH 0/2] IPv6 improvements
Date: Sun, 29 Sep 2013 11:53:27 +0200 [thread overview]
Message-ID: <1380448409-19583-1-git-send-email-eric@regit.org> (raw)
Hello,
This patchset fixes IPv6 prefix computation and adds the
missing part for IPv6 NAT support.
I'm not really happy with the first patch because it seems
the prefixmask is computed during the evaluation. But that
result is not used and the prefix mask is rebuild from the
prefix_len in the netlink phase.
Eric Leblond (2):
fix IPv6 prefix computation.
Add support for IPv6 NAT
src/evaluate.c | 8 ++++++--
src/netlink.c | 11 +++++++----
src/netlink_delinearize.c | 16 ++++++++++++++--
3 files changed, 27 insertions(+), 8 deletions(-)
BR,
--
1.8.4.rc3
next reply other threads:[~2013-09-29 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 9:53 Eric Leblond [this message]
2013-09-29 9:53 ` [nftables PATCH 1/2] fix IPv6 prefix computation Eric Leblond
2013-09-30 10:57 ` Pablo Neira Ayuso
2013-09-29 9:53 ` [nftables PATCH 2/2] Add support for IPv6 NAT Eric Leblond
2013-09-30 10:57 ` Pablo Neira Ayuso
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=1380448409-19583-1-git-send-email-eric@regit.org \
--to=eric@regit.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@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 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).