From: Phil Oester <kernel@linuxace.com>
To: netfilter-devel@lists.netfilter.org
Subject: [PATCH] Cleanup ttl match option parsing
Date: Sun, 22 Aug 2004 10:38:56 -0700 [thread overview]
Message-ID: <20040822173856.GA20772@linuxace.com> (raw)
The below patch allows the ttl match to be used with other matches
without assuming it 'owns' all options. For example, this command
currently causes the '...TTL option twice error':
iptables -A foo -d 1.2.3.4 -m ttl --ttl-eq 1 -m state --state NEW -j ACCEPT
But works with the below patch.
This fixes bugzilla #183
Phil
diff -ru ipt-orig/extensions/libipt_ttl.c ipt-new/extensions/libipt_ttl.c
--- ipt-orig/extensions/libipt_ttl.c 2002-05-29 09:08:16.000000000 -0400
+++ ipt-new/extensions/libipt_ttl.c 2004-08-22 13:07:01.161108504 -0400
@@ -40,10 +40,6 @@
check_inverse(optarg, &invert, &optind, 0);
value = atoi(argv[optind-1]);
- if (*flags)
- exit_error(PARAMETER_PROBLEM,
- "Can't specify TTL option twice");
-
if (!optarg)
exit_error(PARAMETER_PROBLEM,
"ttl: You must specify a value");
@@ -56,8 +52,6 @@
/* is 0 allowed? */
info->ttl = value;
- *flags = 1;
-
break;
case '3':
if (invert)
@@ -66,8 +60,6 @@
info->mode = IPT_TTL_LT;
info->ttl = value;
- *flags = 1;
-
break;
case '4':
if (invert)
@@ -76,14 +68,17 @@
info->mode = IPT_TTL_GT;
info->ttl = value;
- *flags = 1;
-
break;
default:
return 0;
}
+ if (*flags)
+ exit_error(PARAMETER_PROBLEM,
+ "Can't specify TTL option twice");
+ *flags = 1;
+
return 1;
}
next reply other threads:[~2004-08-22 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-22 17:38 Phil Oester [this message]
2004-08-23 18:54 ` [PATCH] Cleanup ttl match option parsing Patrick McHardy
2004-08-23 19:57 ` Phil Oester
2004-08-23 20:45 ` 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=20040822173856.GA20772@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.