iptables: No chain/target/match by that name

serpentor · 01-23-2009, 07:20 PM

I'm consistently getting this error:

Code:

/etc/cron.hourly/portflush:

iptables: No chain/target/match by that name

I read http://www.faqs.org/docs/iptables/commonproblems.html and some of the other threads here, but I'm not sure what I'm looking at.

The output of sudo /sbin/iptables -t filter -L is

Code:

Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         
DROP       all  --  anywhere             81.189.52.37        
DROP       all  --  anywhere             214.109.56.59.broad.fz.fj.dynamic.163data.com.cn

I'm not sure how to sort out whether the solution is to fix a module (er, um, uh, huh?) or to ditch a rule or what. Any ideas? This is kind of feeling greek to me right now.

I tried manually running /etc/cron.hourly/portflush, but got an error:

/etc/cron.hourly/portflush: line 10: iptables: command not found

Line 10 isn't especially illuminating:
$IPTOOL -F $PORTSENTRY_CHAIN

It seems like $IPTOOL isn't defined anywhere. I'm not sure where or how to go about solving that, though.

repo · 01-24-2009, 11:48 AM

could you post the script?

serpentor · 02-03-2009, 01:10 PM

Quote:

Originally Posted by repo

could you post the script?

Here's the script:

Code:

#!/bin/sh

source /etc/sysconfig/portsentry

# This will flush the PORTSEN rules from your firewall tool (ipchains or
# iptables) every hour if CLEAR_CHAIN is set to "1" in the
# /etc/sysconfig/portsentry file 
if [ "$CLEAR_CHAIN" = "1" ]
then
	$IPTOOL -F $PORTSENTRY_CHAIN
	rm -f /var/log/portsentry/*blocked*
fi

exit

I did address the $IPTOOL error, but i definitely get the same error: "iptables: No chain/target/match by that name" when I run the script at the command line, too.

Any ideas?

datopdog · 02-04-2009, 04:25 AM

that is because portsentry is not creating the chain that iptables is trying to flush.

serpentor · 02-05-2009, 10:02 AM

That makes a lot of sense. Is there a right way to address this?