There is a new SuSEfirewall available on the FTP which you should get first...second if you are using DHCP for the interface that is not up before the FW rule script begins look in the script for FW_SERVICE_DHCLIENT="no" change that to yes. Regards, Jon On Thu, 5 Apr 2001, Stephan Dankers wrote:

Hello everybody,

I'm trying to get the SuSEfirewall (Linux 7.1, Kernel 2.2.18) starting.

I am new to Linux and firewalls, so maybe one of the profs, can tell me, what's wrong with my configuration and what the warning message from insmod means, when booting the computer

Is it okay, that the firewall starts before the network adapters are set up ?

Here is an excerpt of the boot.msg file in /var/log

============== START boot.msg ============== Inspecting /boot/System.map-2.2.18

. . . Loaded 10080 symbols from /boot/System.map-2.2.18. Symbols match kernel version 2.2.18.

. . .

INIT: Entering runlevel: 3 Boot logging started at Thu Apr 5 18:05:42 2001 Master Resource Control: previous runlevel: N, switching to runlevel: 3 Starting Firewall Initialization: (phase 1 of 3) (run 2 of 3) insmod: Warning: /lib/modules/2.2.18/net/3c90x.o parameter switchdelay has max < min! Warning: interface eth0 is not active. Warning: interface eth1 is not active. No interfaces active! exiting ... SuSEfirewall: clearing rules now ... done failed Initializing random number generator done Setting up network device eth0 done Setting up network device eth1 done Setting up routing (using /etc/route.conf) done Starting Firewall Initialization: (phase 2 of 3)

. . .

Starting inetd done Starting Firewall Initialization: (phase 3 of 3) Master Resource Control: runlevel 3 has been reached Failed services in runlevel 3: SuSEfirewall_init SuSEfirewall_setup SuSEfirewall_final ============== END boot.msg ==============

Thanks

Stephan

--------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com