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
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
Hi! Sorry for being OT, but I need for my apache-security-update the /etc/rc.status file. This case is quiet serious because when my server crashs down, I wont be able to start my apache... Is it a rpm-Problem of SuSE that they don't include that rc.status-file? On 7.0 and 7.1, it is available out of the box... I used the normal update for 6.4.... Any comments? Thanks, Max
Hi!
Sorry for being OT, but I need for my apache-security-update the /etc/rc.status file.
This case is quiet serious because when my server crashs down, I wont be able to start my apache...
Is it a rpm-Problem of SuSE that they don't include that rc.status-file? On 7.0 and 7.1, it is available out of the box...
I used the normal update for 6.4....
Any comments?
Thanks, Max
Hi Max, we are not aware of a bug wrt /etc/rc.status. I have attached mine... Thanks, Roman. -- - - | Roman Drahtmüller <draht@suse.de> // "Caution: Cape does | SuSE GmbH - Security Phone: // not enable user to fly." | Nürnberg, Germany +49-911-740530 // (Batman Costume warning label) | - -
On Mon, 26 Feb 2001, Roman Drahtmueller wrote:
Sorry for being OT, but I need for my apache-security-update the /etc/rc.status file.
This case is quiet serious because when my server crashs down, I wont be able to start my apache...
Is it a rpm-Problem of SuSE that they don't include that rc.status-file? On 7.0 and 7.1, it is available out of the box...
I used the normal update for 6.4....
Any comments?
Thanks, Max
Hi Max,
we are not aware of a bug wrt /etc/rc.status. I have attached mine...
I ran into the same problems with some of the suse-update-rpm's. Seems that they use the suse 7+ initscripts in the updates, which use rc.status, even for older distributions which do not have this file. Copying the suse 7.0 rc.status-file helped me out - but it is bad that update rpm's can't be used without copying some files manually from newer distributions. c'ya sven -- The Internet treats censorship as a routing problem, and routes around it. (John Gilmore on http://www.cygnus.com/~gnu/)
Hi! ok probably found the answer, did not check it myself yet though. The posting is in german, but i basically says that there are a few lines in the three firewall scripts which are commented out but most probably should be NOT commented out ! If you change those lines everything seems ok and you get no more errors. http://groups.google.com/groups?q=%22Philipp++Schlegel%22&hl=en&lr=&safe=off &rnum=4&seld=924782710&ic=1 mats ----- Original Message ----- From: "semat" <semat@wawa.eahd.or.ug> To: "Ernst Koch" <ernst.koch@gmx.de> Cc: <> Sent: Monday, February 26, 2001 12:51 PM Subject: Re: [suse-security] SuSE 7.1 - firewall
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
--------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com
Ernst; yes, there seems to be a few issues with the Script, especially with DHCP and Dial-up. I have been able to replicate a few of these here now that I have time to play with it all again (SuSE Oakland is closed). What you should do is download the tarball of the new script from suse.de/~marc and se that (not production yet) but this is working for me. I think a lot of the problem was cosmetic, as the chains were built, just had the error after run levels. Regards, Jon 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
participants (7)
-
Ernst Koch -
marsaro＠interearth.com -
mathias rockel -
Max Lindner -
Roman Drahtmueller -
semat -
Sven Koch