Settings via init.d lost during runtime

Settings via init.d lost during runtime

[KKH]

Hi,

I'm using a suse9.1 box with iptables as router/dump for the other 
machines of mine. custom firewall/nat settings are done by a script that 
is linked by 'rc3.d'. the script is like

#!/bin/bash
IPTABLES='/usr/sbin/iptables -v'
echo "Starting NoIP Client..."
/usr/local/bin/noip2
echo "Done"
[...]
echo "Setting more firewall rules..."
$IPTABLES -I INPUT -p tcp -i ppp0 --dport 1337 -j ACCEPT
echo "Done"
[... Executing more tools ...]


now the weird thing is that all tools run by the script are active while 
the iptables settings are not present when the script finishes . 
iptables does not give any error msg - the rules are simply 
ignored/forgotten/whatever.

any idea whats happening?

regards
kkh

RE: Settings via init.d lost during runtime

[Jason Opperisano]

> I'm using a suse9.1 box with iptables as router/dump for the other
> machines of mine. custom firewall/nat settings are done by a script that
> is linked by 'rc3.d'.

are you sure the script is running at boot?  do you see your "echo" statements output to the screen?  i have a firewall on suse 9.0 on which i had to link my firewall startup script in to /etc/init.d/rc2.d.

just a thought...

-j

RE: Settings via init.d lost during runtime

[Jason Opperisano]

> yes. all the tools that are run by the script - also those which are
> executed after iptables - are active after booting..

my guess then, would be that you still have the suse iptables startup script enabled and it is running after your custom script.  the first thing the suse script does, is to flush out all your rules...

disable the suse iptables script from running at boot:

	chkconfig -s SuSEfirewall2_setup off
	chkconfig -s SuSEfirewall2_init off
	chkconfig -s SuSEfirewall2_final off

beyond that--you've stumped me...

-j