I have an existing RH box with my own iptables firewall rules. On RH, I simply have to run this script of mine, then run RH's iptables save. After this my rules take effect whenever RH's firewall startup script executes. I am now moving to SuSE 9.1. While they have a pretty elaborate collection of scripts as part of their SuSEFirewall package, is there a way that I can have their firewall startup scripts use my own rules, without me having to define all the little things in their scripts? Or do I have no choice but to not run their firewall startup scripts and run my own instead? The reason I would rather use their firewall startup scripts (if I can get them to use my rules only) instead of my own is because then I do not have to worry about the firewall startup script execution order. Thanks in advance for any help, -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin First they came for the Jews and I did not speak out because I was not a Jew. Then they came for the Communists and I did not speak out because I was not a Communist. Then they came for the trade unionists and I did not speak out because I was not a trade unionist. Then they came for me and there was no one left to speak out for me. -- Pastor Martin Niemöller
Hi Mobeen. The following applies to SuSE 8.1 pro - should be valid for 9.1 as well. Try taking a look at /etc/init.d/boot.local - a copy below #! /bin/sh # # Copyright (c) 2002 SuSE Linux AG Nuernberg, Germany. All rights reserved. # # Author: Werner Fink <werner@suse.de>, 1996 # Burchard Steinbild <feedback@suse.de>, 1996 # # /etc/init.d/boot.local # # script with local commands to be executed from init on # system startup # # Here you should add things, that should happen directly # after booting # before we're going to the first run level. # # start my own custom firewall now! /home/my/path/to/firewall/script/my-firewall-script # start HD power management spindown HDD's after 2 minutes # inactivity hdparm -S24 /dev/hda hdparm -S24 /dev/hdb hdparm -S24 /dev/hdc # add the TMPDIR environment variable export TMPDIR=/uploads/ I don't use the SuSE Firewall script. The above firewall script is all I have running on my machine - seems adequate for me. SuSEFirewall has been uninstalled. Kind Regards - Keith Roberts On Thu, 22 Jul 2004, Mobeen Azhar wrote:
To: suse-security@suse.com From: Mobeen Azhar <moby@mobsternet.com> Subject: [suse-security] SuSEFirewall2 and custom rules
I have an existing RH box with my own iptables firewall rules. On RH, I simply have to run this script of mine, then run RH's iptables save. After this my rules take effect whenever RH's firewall startup script executes.
I am now moving to SuSE 9.1. While they have a pretty elaborate collection of scripts as part of their SuSEFirewall package, is there a way that I can have their firewall startup scripts use my own rules, without me having to define all the little things in their scripts? Or do I have no choice but to not run their firewall startup scripts and run my own instead?
The reason I would rather use their firewall startup scripts (if I can get them to use my rules only) instead of my own is because then I do not have to worry about the firewall startup script execution order.
Thanks in advance for any help,
-- --Moby
They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin
First they came for the Jews and I did not speak out because I was not a Jew. Then they came for the Communists and I did not speak out because I was not a Communist. Then they came for the trade unionists and I did not speak out because I was not a trade unionist. Then they came for me and there was no one left to speak out for me. -- Pastor Martin Niemöller
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here
participants (2)
-
Mobeen Azhar
-
suse@karsites.net