From owner-freebsd-current Sun Dec 27 07:53:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05022 for freebsd-current-outgoing; Sun, 27 Dec 1998 07:53:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05008 for ; Sun, 27 Dec 1998 07:53:05 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id PAA02315; Sun, 27 Dec 1998 15:51:49 GMT Date: Sun, 27 Dec 1998 15:51:42 +0000 (GMT) From: Doug Rabson To: Stefan Eggers cc: Mike Smith , Erik Funkenbusch , freebsd-current@FreeBSD.ORG Subject: Re: Broken ipfw? In-Reply-To: <199812271249.NAA01891@semyam.dinoco.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Dec 1998, Stefan Eggers wrote: > > Please do. It would be very useful to know if the SYSINIT for ipfw is > > being called correctly. > > For further investigation I added printf's to ipfw_load and ipfw_mod as > their first statement to see if they get called. Nothing from them > though the SYSINIT should call module_register_init which should then > call ipfw_load. So either the SYSINIT doesn't get recognized or it > might go wrong in module_register_init. I haven't investigated that > further, yet as I first had to find out who does the SYSINIT and how. > > I also modified kern_linker.c to give me debug output. Comparing it > to what other kernel modules produce this looks normal. Due to the > length of the logged data I don't want to append it here. Everyone > asking for a copy can get one by private mail. > > What I noticed was that during startup /etc/rc.firewall tries to > determine if there is an ipfw module loaded or something in the kernel > it sees nothing, tries to load the module and the result is that it > gets reported along the lines "module already loaded, incrementing use > counter." > > So far what I got by now. > > Stefan. Is the module being correctly linked with setdef0.o and setdef1.c to define the linker sets? It should be if its built using the standard bsd.kmod.mk but its worth checking. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message