No, actually, that will still fail. test "$FW_START" = yes || exit 0 is in the firewall script. You might think that if you manually start it, it should work, but not under SuSE. I suppose you could edit /etc/rc.d/init.d/firewall to have a "do-it-dammit" command, but it seems like more work than an admin should have to do. If I call "./firewall start", I expect the firewalling code to start. Period. If SuSE wants to use silly "FW_START" environment variables, let them write something that parses /etc/rc.config and creates/unlinks the /etc/rcX.d/* symlinks appropriately. D At 01:30 PM 3/25/00 +1200, Michael Doerner wrote:
Robert,
Sorry if that's too obvious, but I thought it's better to ask: Apparently you don't start the firewall automatically at system start-up (FW_START=no) so you must start it manually (i.e. /sbin/init.d/firewall start or rcfirewall start)?
FW_START="no" FW_LOCALNETS="192.168.0.0/24" FW_FTPSERVER="" FW_WWWSERVER="" FW_SSLSERVER="" FW_SSLPORT="" FW_MAILSERVER="199.218.243.183" FW_DNSSERVER="" FW_NNTPSERVER="" FW_NEWSFEED="" FW_WORLD_DEV="ppp0" FW_INT_DEV="eth0" FW_LOG_ACCEPT="no" FW_LOG_DENY="yes" FW_ROUTER="" FW_FRIENDS="no" FW_INOUT="no" FW_SSH="no" FW_TRANSPROXY_OUT="" FW_TRANSPROXY_IN="" FW_REDIRECT="" FW_TCP_LOCKED_PORTS="1:1023" FW_UDP_LOCKED_PORTS="1:1023"
Regards, Michael Doerner
-- 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/Doku/FAQ/
-- 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/Doku/FAQ/