From: Jon Jacobsen <jonj@at...> - 2007-06-19 17:20:46
> I have succesfully installed and configured the last Firewall
> Builder release on Opensuse 10.2.
> Everything works fine so far.
> I have just the problem, that the firewallname.fw script is NOT
> automatically executed on machine startup.
> What I have done is:
> - I have modified the path in "/etc/init.d/firewall" to reflect the
> correct fw file
> After booting up the machine I get this status:
> susi:~ # /etc/init.d/firewall status
> Checking for Firewall (iptables
> v1.3.6) running
> But the firewall is NOT ACTIVE.
> A manuel restart helps, makes the firewall rules active:
> susi:~ # /etc/init.d/firewall restart
> Firewall done
> Starting Firewall (iptables v1.3.6)
> Activating firewall script generated Tue Jun 19 10:25:50 2007 by
> Rule 0 (eth0)
> Rule 1 (lo)
> Rule 3 (global)
> Rule 4 (global)
> Rule 5 (global)
> Now I would like to get this done automatically.
> Any idea how?
> the command "/etc/init.d/firewall stop" excludes me out... Is this
> a normal behaviour?
> Thanks for letting me know.
> Psssst! Schon vom neuen GMX MultiMessenger geh?rt?
> Der kanns mit allen: http://www.gmx.net/de/go/multimessenger
I use Suse on several firewalls and just use a quick script for the install script that basically does 'cp (name).fw /etc/init.d/firewall;/etc/init.d/firewall'
Fwbuilder doesn't run on my firewall, so I need to scp the file. I don't have a case statement for stop, etc. but why would you ever stop a firewall on a production box?
Make sure and run 'chkconfig -l firewall' to make sure it "on" for your init level. The fwbuilder script will now start during init.
"First they ignore you. Then they laugh at you. Then they fight you. Then you win." Mohandas Gandhi
Get latest updates about Open Source Projects, Conferences and News.