diff options
author | Phil Oester <kernel@linuxace.com> | 2013-10-08 09:20:15 -0700 |
---|---|---|
committer | Pablo Neira Ayuso <pablo@netfilter.org> | 2013-11-03 21:25:15 +0100 |
commit | 9b3fd1352c9806ef5acc10f38b1131bc2f62b60c (patch) | |
tree | 7b4135337645d51a461f9cfb3d0293db4947db62 /extensions/libxt_connlabel.c | |
parent | e0853f3c285a6ad082e5ed5ff5e308beeeba41d9 (diff) |
iptables: spurious error in load_extension
In commit 927385017047d (iptables: improve error reporting with extension
loading troubles), a new error message was added in an attempt to handle
the case where a match does not support a particular protocol family.
For instance, attempting to use the osf match on IPv6.
Unfortunately, this error message now triggers when creating a new chain
which has the same name as a match extension, because iptables calls
xtables_find_target with the name of the new chain to verify it does not
clash with an existing target. For example:
# iptables -N tcp
/usr/lib/xtables/libxt_tcp.so: no "tcp" extension found for this protocol
I attempted to resolve this by adding a new XTF flag, but that required changes
in many different places (including -j handling). It seems easiest just to
remove this warning and stick with the original error message of ENOENT, even
if less than precise.
Signed-off-by: Phil Oester <kernel@linuxace.com>
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Diffstat (limited to 'extensions/libxt_connlabel.c')
0 files changed, 0 insertions, 0 deletions