From: Eric Leblond <eric@regit.org>
To: netfilter-devel@vger.kernel.org, pablo@netfilter.org
Cc: eric@regit.org
Subject: [nftables PATCH 1/2] fix IPv6 prefix computation.
Date: Sun, 29 Sep 2013 11:53:28 +0200 [thread overview]
Message-ID: <1380448409-19583-2-git-send-email-eric@regit.org> (raw)
In-Reply-To: <1380448409-19583-1-git-send-email-eric@regit.org>
The prefix building algorithm in netlink phase was incorrect in
IPv6.
For example, when adding the following rule
nft add rule ip6 nat postrouting ip6 saddr 2::/64 --debug=all
we had:
ip6 nat postrouting 0 0
[ payload load 16b @ network header + 8 => reg 1 ]
[ bitwise reg 1 = (reg=1 & 0x00000000 0x99361540 0x00007f8d 0x2e33a1eb ) ^ 0x00000000 0x00000000 0x00000000 0x00000000 ]
[ cmp eq reg 1 0x00000200 0x00000000 0x00000000 0x00000000 ]
With the patch the result is as expected:
ip6 nat postrouting 0 0
[ payload load 16b @ network header + 8 => reg 1 ]
[ bitwise reg 1 = (reg=1 & 0xffffffff 0xffffffff 0x00000000 0x00000000 ) ^ 0x00000000 0x00000000 0x00000000 0x00000000 ]
[ cmp eq reg 1 0x00000200 0x00000000 0x00000000 0x00000000 ]
Signed-off-by: Eric Leblond <eric@regit.org>
---
src/netlink.c | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/src/netlink.c b/src/netlink.c
index c48e667..b1e44ad 100644
--- a/src/netlink.c
+++ b/src/netlink.c
@@ -234,7 +234,8 @@ static void netlink_gen_verdict(const struct expr *expr,
static void netlink_gen_prefix(const struct expr *expr,
struct nft_data_linearize *data)
{
- uint32_t i, cidr, idx;
+ uint32_t idx;
+ int32_t i, cidr;
uint32_t mask;
assert(expr->ops->type == EXPR_PREFIX);
@@ -242,11 +243,13 @@ static void netlink_gen_prefix(const struct expr *expr,
data->len = div_round_up(expr->prefix->len, BITS_PER_BYTE);
cidr = expr->prefix_len;
- for (i = 0; i < data->len; i+= 32) {
+ for (i = 0; (uint32_t)i / BITS_PER_BYTE < data->len; i += 32) {
if (cidr - i >= 32)
- mask = 0;
+ mask = 0xffffffff;
+ else if (cidr - i > 0)
+ mask = (1 << (cidr - i)) - 1;
else
- mask = (1 << cidr) - 1;
+ mask = 0;
idx = i / 32;
data->value[idx] = mask;
--
1.8.4.rc3
next prev parent 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 [nftables PATCH 0/2] IPv6 improvements Eric Leblond
2013-09-29 9:53 ` Eric Leblond [this message]
2013-09-30 10:57 ` [nftables PATCH 1/2] fix IPv6 prefix computation 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-2-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).