From: Phil Oester <kernel@linuxace.com>
To: netfilter-devel@lists.netfilter.org
Subject: [PATCH] iptables: handle cidr notation more sanely
Date: Sun, 9 Jul 2006 15:28:18 -0700 [thread overview]
Message-ID: <20060709222818.GA23200@linuxace.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 452 bytes --]
At present, a command such as
iptables -A foo -s 10.10/16
will interpret 10.10/16 as 10.0.0.10/16, and after applying the mask end
up with 10.0.0.0/16, which likely isn't what the user intended. Yet
some people do expect 10.10 (without the cidr notation) to end up as
10.0.0.10.
The below patch should satisfy all parties. It zero pads the missing
octets only in the cidr case, leaving the IP untouched otherwise.
This resolves bug #422
Phil
[-- Attachment #2: patch-cidr --]
[-- Type: text/plain, Size: 1058 bytes --]
diff -ru ipt-orig/iptables.c ipt-new/iptables.c
--- ipt-orig/iptables.c 2006-04-21 05:04:51.000000000 -0700
+++ ipt-new/iptables.c 2006-07-09 15:15:15.000000000 -0700
@@ -583,6 +583,34 @@
return (char *) NULL;
}
+static void
+pad_cidr(char *cidr)
+{
+ char *p, *q;
+ unsigned int onebyte;
+ int i, j;
+ char buf[20];
+
+ /* copy dotted string, because we need to modify it */
+ strncpy(buf, cidr, sizeof(buf) - 1);
+ buf[sizeof(buf) - 1] = '\0';
+
+ p = buf;
+ for (i = 0; i <= 3; i++) {
+ if ((q = strchr(p, '.')) == NULL)
+ break;
+ *q = '\0';
+ if (string_to_number(p, 0, 255, &onebyte) == -1)
+ return;
+ p = q + 1;
+ }
+
+ /* pad remaining octets with zeros */
+ for (j = i; j < 3; j++) {
+ strcat(cidr, ".0");
+ }
+}
+
/*
* All functions starting with "parse" should succeed, otherwise
* the program fails.
@@ -651,6 +679,8 @@
if ((p = strrchr(buf, '/')) != NULL) {
*p = '\0';
addrp = parse_mask(p + 1);
+ if (strrchr(p + 1, '.') == NULL)
+ pad_cidr(buf);
} else
addrp = parse_mask(NULL);
inaddrcpy(maskp, addrp);
next reply other threads:[~2006-07-09 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 22:28 Phil Oester [this message]
2006-07-10 4:26 ` [PATCH] iptables: handle cidr notation more sanely Patrick McHardy
2006-07-10 5:59 ` Patrick Schaaf
2006-07-10 6:43 ` Patrick McHardy
2006-07-10 6:52 ` Patrick Schaaf
2006-07-10 7:24 ` Patrick McHardy
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=20060709222818.GA23200@linuxace.com \
--to=kernel@linuxace.com \
--cc=netfilter-devel@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.