Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "David Ashwood" <david@inspiredthinking.co.uk>
To: netfilter@lists.netfilter.org
Subject: RE: Log Problem
Date: Mon, 9 Aug 2004 19:11:18 +0200	[thread overview]
Message-ID: <200408091311314.SM01376@Hope> (raw)
In-Reply-To: <200408091758.59638.Antony@Soft-Solutions.co.uk>


Thanks for responding Anthony,

1) Same problem as before ' iptables: No chain/target/match by that name'

2) User defined chains work - and I can put a drop rule without problems.

Kernel:
A new box just bought - I thought the kernel was old - but I had to demo a
product for a client - and wanted to get that done before I pester the VPS
hosts to upgrade the kernel.

I can see the libraries on the box for both logging and User Space Logging -
seeing if their being used is harder to establish.

I guess the kernel install didn't do a proper job of installing iptables.


David

-----Original Message-----
From: netfilter-admin@lists.netfilter.org
[mailto:netfilter-admin@lists.netfilter.org] On Behalf Of Antony Stone
Sent: Monday, August 09, 2004 6:59 PM
To: netfilter@lists.netfilter.org
Subject: Re: Log Problem

On Monday 09 August 2004 5:40 pm, 'Me' wrote:

>  Hi,
> I'm having problems logging packets (IPTables: 1.2.8 Kernel: 2.4.8) with
> the following rule (from the  FAQ):
>
> iptables -N logdrop
> iptables -A logdrop -j LOG
> iptables -A logdrop -j DROP
>
> On the log line I get:
> iptables: No chain/target/match by that name
>
> I'm a little lost - any pointers?

It seems unlikely, but has your kernel been compiled without support for the

LOG target (and by the way, why are you using a three year old kernel 
anyway?)?

Test one thing at a time:

1. Can you use the LOG target?
iptables -A INPUT -j LOG

2. Can you put a rule into a user-defined chain?
iptables -N logdrop
iptables -A logdrop -j DROP

If both the above tests work, then there is no reason you shouldn't be able
to 
put a LOG target into your user-defined chain (so check very carefully the 
syntac of what you are typing when you get the error, etc).

If one of the above tests fails, you know where the problem is.

Just one last thing to check - you haven't compiled the userspace iptables 
tool without also recompiling the kernelspace netfilter part, have you?

If you do one of these, you should also do the other to match.

Regards,

Antony.

-- 
Microsoft may sell more software than any other company, but McDonald's sell

more burgers than any other company, and I think the other similarities are 
obvious...

                                                     Please reply to the
list;
                                                           please don't CC
me.







  parent reply	other threads:[~2004-08-09 17:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09 16:40 Log Problem 'Me'
2004-08-09 16:58 ` Antony Stone
2004-08-09 17:05   ` Eric Ellis
2004-08-09 17:34     ` Antony Stone
2004-08-09 17:11   ` David Ashwood [this message]
2004-08-09 17:37     ` Antony Stone
2004-08-09 19:33       ` David Ashwood
  -- strict thread matches above, loose matches on Subject: below --
2004-08-09 16:30 David Ashwood

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=200408091311314.SM01376@Hope \
    --to=david@inspiredthinking.co.uk \
    --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