* no chain/target/match for LOG module even though the shared library exists
@ 2002-09-23 14:22 Martin Robb
0 siblings, 0 replies; only message in thread
From: Martin Robb @ 2002-09-23 14:22 UTC (permalink / raw)
To: netfilter
Greetings,
I'm running iptables on a 2.4.14 lsm kernel on what was, originally at
least, a RHL 7.1 system. When I try using the LOG feature, e.g.:
iptables -A INPUT -j LOG
I get the error:
No chain/target/match by that name.
I apologize if this problem has already been dealt with on the list, but
I couldn't find it in the FAQ and the list archives don't appear to be
searchable.
I've tried the same syntax on a Debian system (2.4.18 kernel) and it
accepts it fine, so it doesn't look like a syntax problem. I have
upgraded iptables to 1.2.6a on the 2.4.14 kernel, which is the same
iptables version running on the Debian system (BTW, there appear to be
some header file discrepencies when I tried to compile 1.2.7a against
the 2.4.14 kernel). I have even tried applying all cleanly patching
patch-o-matic patches and still get the problem.
The /lib/iptables/libipt_LOG.so library exists (root root 755) and
besides, if I give it a bogus module name like:
iptables -A INPUT -j foobar
I get a totally different error:
... /lib/iptables/libipt_foobar.so: cannot open shared object file ...
I'm stumped. Can anyone tell me what I need to do to get logging
working on this system?
Thanks,
Martin Robb
MartinRobb@ieee.org
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2002-09-23 14:22 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-09-23 14:22 no chain/target/match for LOG module even though the shared library exists Martin Robb
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.