Maybe change the number of the start script in the boot process to a larger one that comes after the interface is up that should solve the issue. Look at /sbin/init.d/rc2.d/S*firewall_init or something similar On Mon, 26 Feb 2001, Ernst Koch wrote:
On the installation we have the following problem: the first time the firewall script runs the Network is not up so we only get an error message.
Can someone tell me if this is normal or how I can fix this.
I have got the same problem. How can I start the firewall *after* the network (ippp0) was started?
Regards Ernst
-- Sent through GMX FreeMail - http://www.gmx.net
--------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com