iptables prob in /var/log/messages
 

Hi all

i get this message in my /var/log/message file.

Nov 8 06:06:16 localhost ifup: iptables: No chain/target/match by that name
Nov 8 06:06:16 localhost ifup: iptables: Table does not exist (do you need to insmod?)

can anyone enlighten me on this message and a possible cure. As far as i know the iptables are configured correct, and have not been moved from default locations. I'm running RH9 with a 2.4.20 kernel.

regards
GT

This is a mesage from the /sbin/ifup script..

It tries to open a DNS path through the LOKKIT firewall script if it is active..
Both that script and the /etc/sysconfig/network-scripts/ifup-post script..

It may be that you have two iptables scripts starting but the ifup script is remembering just the first one..

Hi


so does that mean the iptables are not initialised/started/working???????? either way is there a way i can fix it. this seems to be a default prob with RH9 as i've just installed RH9 on an old laptop, and i find the same entries in the log files. by the way what should the read/write permissions be on the /etc/sysconfig/iptables. it apears that they are read only for owner (root) is this correct?
thanks
GT

The permissions are correct.

If you just want to see your rules then try:
itpables -nL

Thanks for the info on permissions, but i'm still no wiser or closer to a solution to my original dillema, surely someone out there can help.

Can and how do i fix the prob???

Is my firewall running (Y/N)???

i tried to move this thread to the Networking forum in the hope that some networking guru could help. but i was read the riot act before being taken outside and shot for my insolence. :tisk: consequently the thread was shut down and i have to remain here until i get an answer. :cry:

regards
GT

"The technology that preserved the balance of our history - between uses of our culture that were free and uses of our culture that were only upon permission - has been undone. The consequence is that we are less and less a free culture, more and more a permission culture"
Lawrence Lessig, Free Culture, :eek:
blogspace.com/freeculture/introduction

Is my firewall running (Y/N)???
service iptables status
chkconfig --list | grep iptables

i tried to move this thread to the Networking forum in the hope that some networking guru could help. but i was read the riot act before being taken outside and shot for my insolence. :tisk: consequently the thread was shut down and i have to remain here until i get an answer. :cry:
We like to keep thinks all in one place so that multiple people aren't all working on the same problem independently. Please try to be patient when waiting for replies (alot of us here have jobs/schoool and whatnot). :)

Hi Capt

i appreciate your thoughts. but as, after 6 days of this post being in the security forum and still not getting an answer, which probably means that this is not the best forum to post this query, is it possible i can be freed from here and post this query in another forum????????? Although our banter has been fun, it's neither fishing nor mending the net as it were.
Regards
GT

is it possible i can be freed from here and post this query in another forum?????????

Done. Thread moved to the linux - networking forum

Hi Capt

thanks for the move. greatly appreciated.

the output from the chkconfig --list | grep iptables is as follows

0 off 1 off 2 on 3 on 4 on 5 on 6 off

I'm not sure on the output, but as an educated guess, does this mean that runlevels 2, 3, 4 & 5 have iptables running?

if i have the iptables running, is there anyway i can fix the ifup scripts to stop giving me the error at boot?
regards
GT

You will have iptables running, just need to be sure only 1 script starts tho'..
/etc/init.d/iptables gets it's rules from /etc/sysconfig/iptables

Remove iptables from the startup sequence, chkconfig --del iptables and see if any other rules are being loaded at boot time..
Do iptables-save to list them on the screen..

If there are any other rules loading, find out where from and decide which ones to keep.
To restore iptables in the startup, do chkconfig --add iptables