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@xxxxxxxxxxxxxxxxxxxxxx]
Sent: maandag 20 oktober 2003 0:41
To: techmail@xxxxxxxxxxxx
Subject: RE: Debugging
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..
George Vieira
Citadel
Computer Systems Pty Ltd
http://www.citadelcomputer.com.au
-----Original Message-----
From: techmail@xxxxxxxxxxxx
[mailto:techmail@xxxxxxxxxxxx]
Sent: Monday, 20 October 2003 8:24
AM
To: netfilter@xxxxxxxxxxxxxxxxxxx
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
