]> git.ipfire.org Git - thirdparty/iptables.git/commitdiff
iptables-compat: homogenize error messages with 'R' option
authorAna Rey <anarey@gmail.com>
Wed, 5 Nov 2014 15:46:34 +0000 (16:46 +0100)
committerPablo Neira Ayuso <pablo@netfilter.org>
Sun, 9 Nov 2014 15:23:03 +0000 (16:23 +0100)
There is a difference between error messages in iptables and
iptables-compat:

 # iptables -R INPUT 23 -s 192.168.2.140 -j ACCEPT
iptables: Index of replacement too big.
 # iptables-compat -R INPUT 23 -s 192.168.2.140 -j ACCEPT
iptables: No chain/target/match by that name.

Now, iptables-compat shows the same error message than iptables in
this case.

Signed-off-by: Ana Rey <anarey@gmail.com>
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
iptables/nft.c

index 6cb03a0dba9b1760ecf1b5f8c80aa6fd05443a8b..64222af8d0b37b580afd395d4eac955042988cfc 100644 (file)
@@ -2358,7 +2358,7 @@ const char *nft_strerror(int err)
            { nft_chain_user_add, EEXIST, "Chain already exists" },
            { nft_rule_add, E2BIG, "Index of insertion too big" },
            { nft_rule_check, ENOENT, "Bad rule (does a matching rule exist in that chain?)" },
-           { nft_rule_replace, E2BIG, "Index of replacement too big" },
+           { nft_rule_replace, ENOENT, "Index of replacement too big" },
            { nft_rule_delete_num, E2BIG, "Index of deletion too big" },
 /*         { TC_READ_COUNTER, E2BIG, "Index of counter too big" },
            { TC_ZERO_COUNTER, E2BIG, "Index of counter too big" }, */