Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Martin Robb <MartinRobb@ieee.org>
To: netfilter@lists.netfilter.org
Subject: no chain/target/match for LOG module even though the shared library exists
Date: Mon, 23 Sep 2002 10:22:59 -0400	[thread overview]
Message-ID: <3D8F23C3.6050009@ieee.org> (raw)

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




                 reply	other threads:[~2002-09-23 14:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3D8F23C3.6050009@ieee.org \
    --to=martinrobb@ieee.org \
    --cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox