From owner-freebsd-current Sun Dec 27 04:53:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA20333 for freebsd-current-outgoing; Sun, 27 Dec 1998 04:53:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA20328 for ; Sun, 27 Dec 1998 04:53:49 -0800 (PST) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id NAA06486; Sun, 27 Dec 1998 13:51:34 +0100 (MET) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id NAA01891; Sun, 27 Dec 1998 13:49:41 +0100 (CET) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199812271249.NAA01891@semyam.dinoco.de> To: Mike Smith cc: "Erik Funkenbusch" , freebsd-current@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: Broken ipfw? In-reply-to: Your message of "Sat, 26 Dec 1998 13:57:37 PST." <199812262157.NAA01523@dingo.cdrom.com> Date: Sun, 27 Dec 1998 13:49:40 +0100 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message