Skip to contentSkip to conversation

Don't understand these errors with logdrop target

DISCUSSION Steve Comfort 2 participants 2 messages Aug 25, 2004

lore
Share & tools
lore
#0 lore 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

#1 lore raw
Quoted 2 lines · Steve Comfort

echo 2
$IPTABLES -P INPUT LOGDROP

[...]

Quoted 3 lines

2
iptables: Bad policy name
The question is : Why does using LOGDROP as a policy cause these errors?

Because only builtin targets can be used as policy, meaning ACCEPT and DROP. If you want to use your LOGDROP as "policy", then you'll have to keep it as last chain rule...

Signature · 2 lines
http://www.netexit.com/~sid/
PGP KeyID: 157E98EE FingerPrint: FA62226DA9E72FA8AECAA240008B480E157E98EE
Quoted 2 lines
Quoted 2 lines

Hi! I'm your friendly neighbourhood signature virus. Copy me to your signature file and help me spread!