For the first problem, I would look into /etc/init.d/rc2.d and /etc/init.d/rc3.d and see if
there are any SuSEfirewall scripts (not SuSEfirewall2). If there are, then you should either
delete them or rename them with something in front of the K## ot S## (the K## and S##
tell the system to start these in order on startup of kill them).
For your second problem, what version of firewall2 are you running. There is a version
2.1 at /www.suse.com/~marc/suse which does not seem to have the lockup behavior.
Also, there was a previous post on here in which a few lines in a script could be
commented out which ended this. Maybe someone who also had this problem could help
out.
Jim
12/16/01 01:30:11 PM, FX Fraipont
Two problems since moving from SuSefirewall to SuSefirewall 2:
1. On boot, I get a series of "Ipchains : protocol not available" messages. Fair enough, if SuSEfirewall2 uses Iptables. But How do I get rid of the message? I have disabled SuSefirewall in rc.config.
2. I connect via isdn. If I hang up, then shutdown, the computer locks at "shutting down firewall", and does not power down. However, if I don't hangup, shutdown proceeds smoothly, I get a few error messages regarding route and ippp0, but the computer shuts down. This is particularly annoying since my computer masquerades to a network, and if my son tries shutting down my computer remotely, I find in the morning that my computer is still on, stuck at the "shutting down firewall" stage.
Any advice?
Thanks
fx
-- _______________________ Courtesy of SuSE Linux AIM fyxyf
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com