Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 27 Dec 1998 15:51:42 +0000 (GMT)
From:      Doug Rabson <dfr@nlsystems.com>
To:        Stefan Eggers <seggers@semyam.dinoco.de>
Cc:        Mike Smith <mike@smith.net.au>, Erik Funkenbusch <erikf@visi.com>, freebsd-current@FreeBSD.ORG
Subject:   Re: Broken ipfw? 
Message-ID:  <Pine.BSF.4.01.9812271550380.380-100000@herring.nlsystems.com>
In-Reply-To: <199812271249.NAA01891@semyam.dinoco.de>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.01.9812271550380.380-100000>