RE: Debugging

RE: Debugging

[techmail]

[-- Attachment #1: Type: text/plain, Size: 1930 bytes --]

That did the trick. Stupid not to notice it, but indeed, the iptables
file wasn't present in /etc/sysconfig, so I did "service iptables save"
and it saved the ruleset (which is non-existent atm). Afterwards the
service came online as expected. Now I can get back to learning how to
write the rules ;-)

 

Thanks!

 

Robert Hazenveld

 

-----Original Message-----
From: George Vieira [mailto:georgev@citadelcomputer.com.au] 
Sent: maandag 20 oktober 2003 0:41
To: techmail@safe2surf.nl
Subject: RE: Debugging

 

vi /etc/init.d/iptables

 

check inside for anything it's testing for to exist before it'll even
run the script.

From memory it checks for /etc/sysconfig/iptables file which contains
the rules you want to add to the machine, if this doesn't exist then the
script stops..

 

I would remove all of the script contents and write your own iptables
script, it's not hard once you know exaclty what you want for a
firewall..

 

Thanks,

 

____________________________________________
George Vieira
Citadel Computer Systems Pty Ltd   Systems Manager   georgev AT
citadelcomputer DOT com DOT au   

Citadel Computer Systems Pty Ltd

Phone : +61 2 9955 2644   HelpDesk: +61 2 9955 2698
<http://www.citadelcomputer.com.au/>  http://www.citadelcomputer.com.au
<http://www.citadelcomputer.com.au/>  

 

 

-----Original Message-----
From: techmail@safe2surf.nl [mailto:techmail@safe2surf.nl]
Sent: Monday, 20 October 2003 8:24 AM
To: netfilter@lists.netfilter.org
Subject: Debugging

Hi,

 

Perhaps this is a stupid question which has been asked too many times,
but I wasn't able to find it.

 

If I do "service iptables start" nothing happens, so when I do "service
iptables status" it says "Firewall is stopped."

 

Because I want to know where in the process the error is I'd like to
know how to debug it. Is there any information on debugging to see what
error it displays?

 

Kind regards,

 

Robert Hazenveld


[-- Attachment #2: Type: text/html, Size: 11461 bytes --]

RE: Debugging

[Daniel Chemko]

This is a redhat bug, not netfilter.

If you are adept at bash scripting, you may want to try bash -x service firewall start.

Enjoy!



-----Original Message-----
From:	techmail@safe2surf.nl [mailto:techmail@safe2surf.nl]
Sent:	Sun 10/19/2003 3:24 PM
To:	netfilter@lists.netfilter.org
Cc:	
Subject:	Debugging
Hi,

 

Perhaps this is a stupid question which has been asked too many times,
but I wasn't able to find it.

 

If I do "service iptables start" nothing happens, so when I do "service
iptables status" it says "Firewall is stopped."

 

Because I want to know where in the process the error is I'd like to
know how to debug it. Is there any information on debugging to see what
error it displays?

 

Kind regards,

 

Robert Hazenveld

Debugging

[techmail]

[-- Attachment #1: Type: text/plain, Size: 437 bytes --]

Hi,

 

Perhaps this is a stupid question which has been asked too many times,
but I wasn't able to find it.

 

If I do "service iptables start" nothing happens, so when I do "service
iptables status" it says "Firewall is stopped."

 

Because I want to know where in the process the error is I'd like to
know how to debug it. Is there any information on debugging to see what
error it displays?

 

Kind regards,

 

Robert Hazenveld


[-- Attachment #2: Type: text/html, Size: 2663 bytes --]