> 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
