Rene Salmon wrote:
Thanks for the reply. Currently the we have a bunch of redhat boxes these boxes have a script "/etc/init.d/iptables" this script loads the iptables modules on to the kernel at startup and then it reads the iptable rules from the file /etc/sysconfig/iptables.
I would like to reuse the /etc/sysconfig/iptables rules file on the Suse box but I do not have the /etc/init.d/iptables startup script for Suse.
I guess I can copy the one from the redhat box and edit it to work with the SuSe box but I really do not know how well that will work.
Thanks Rene
Disable SuSEFirewall2 using chkconfig & call your file from boot.local or your own rc.local file. How are you calling iptables now ?
They have a skeleton file (/etc/init.d/skeleton) which you can modify into the equivalent of your old /etc/init.d/iptables file, you could even name it iptables. Have that file call your /etc/sysconfig/iptables file (installed wherever you want it, maybe as /etc/init.d/iptables.rules or some such) to run the rules. Read the man pages on insserv & chkconfig, they will help. This is quite similar to what I did on this box, & it's been working fine for over a year now, under SuSE 8.2, but I don't think there are any material differences in the init.d setup.