All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Comfort <steve@4Dllc.com>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Don't understand these errors with logdrop target
Date: Wed, 25 Aug 2004 10:36:30 +0200	[thread overview]
Message-ID: <412C4F8E.8010600@4Dllc.com> (raw)

Hi All,

Below is a snippet from my setup script :

        echo 1

        $IPTABLES -N LOGDROP
        $IPTABLES -A LOGDROP -j LOG --log-level debug
        $IPTABLES -A LOGDROP -j DROP

        echo 2

        $IPTABLES -P INPUT LOGDROP
       
        echo 3
       
        $IPTABLES -P OUTPUT LOGDROP
       
        echo 4
       
        $IPTABLES -P FORWARD LOGDROP

        echo 5

When this is run, I see the output below (the echo's are just to zone in 
on the exact rule(s) generating errors):

1
2
iptables: Bad policy name
3
iptables: Bad policy name
4
iptables: Bad policy name
5

The question is : Why does using LOGDROP as a policy cause these errors?

(I have CONFIG_IP_NF_TARGET_LOG set BTW).

Best regards
Steve Comfort



             reply	other threads:[~2004-08-25  8:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-25  8:36 Steve Comfort [this message]
2004-08-25  8:49 ` Don't understand these errors with logdrop target Cedric Blancher

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=412C4F8E.8010600@4Dllc.com \
    --to=steve@4dllc.com \
    --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 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.